WorkSystemsWhat we buildFlow AboutJourneyContact Book a 15-min call
// AEVYX · FINANCE AND OPERATIONS SYSTEMS

Your money is leaking through a system nobody owns.

Settlements that were never reconciled. Courier deductions nobody audited. Margin per SKU that only exists once a quarter, in a spreadsheet, roughly. We find that money in your own files, then we build the system that keeps it shut. Three layers, built in that order, and at the end the brand owns all of it.

13LIVE SYSTEMS3LAYERS1CODEBASE YOU OWN0PER-USER FEES

This page is the map of what gets built. If you want the money found first, that is Flow, and it starts free on last month's files. Find the money, fix the system, keep it shut →

Layer 01Finance and operations · where it starts

The money layer comes first, because it pays for the rest.

Every engagement starts here. Not because it is the biggest build, but because it is the one that puts a rupee number on the table in week one and keeps billing from month one. More than thirty lakh found in client books came out of this work.

reconciliation

Settlement, line by line

Gateway and marketplace payouts matched back to the orders that caused them, through the month rather than at filing time.

  • Every payout traced to its orders, fees and reversals
  • Short-paid and unsettled orders surfaced while they can still be chased
  • The same bill paid twice, caught before it leaves the bank
  • Books and settlements agreeing before your accountant asks
audits

Deduction and courier audits

Freight billed against the weight that actually shipped, and every deduction tested against the rate card you signed.

  • Billed weight against actual, per shipment, per carrier
  • Deductions, penalties and reversals read against the contract
  • RTO and partial-payment cases that quietly never came back
  • The numbers to reopen a rate conversation and win it
margin

Margin per SKU, per channel

Contribution margin computed from the system of record, not assembled by hand once a quarter.

  • True landed cost against true realised price
  • Per SKU, per channel, per store, side by side
  • The SKUs that sell well and earn nothing, named
  • Discounting and returns priced into the margin, not ignored
compliance

GST that fills itself

The recurring grind turned into a checklist built from your own transactions, with the awkward cases handled.

  • Returns prepared from transaction data, not retyped
  • Input credit matched rather than assumed
  • Margin scheme under Rule 32(5) handled for consignment stock
  • Your own adviser keeps the tax treatment and the filing
cashflow

Cashflow and unit economics

A week-by-week view of what lands and what leaves, with the saving sitting in it as a line.

  • Receivables, GST, payroll and supplier dues on one timeline
  • The week that sits closest to the floor, visible today
  • Working capital read against stock ageing, not guessed
  • Unit economics a founder can argue in rupees
keep it shut

Automation that holds the fix

A fix that depends on somebody remembering comes back next quarter, so it gets built into software instead.

  • The reconciliation runs on a schedule, not on a person
  • An alert the moment a rate creeps or a margin slips on a SKU
  • Findings become tickets with an owner and a due date
  • A monthly reporting pack generated, not assembled
Layer 02Retail systems · the proof this is real software

A finance layer is only as honest as the system underneath it.

Most of the leaks above exist because billing, stock and orders live in three places that disagree. So the studio builds the thing underneath too, and it is production software rather than a script: a multi-store web POS and ERP on Next.js, TypeScript and PostgreSQL. It is also the clearest evidence that what you are buying gets built properly.

pos 2.0

Multi-store POS and ERP

Billing at the counter, fast enough for a queue, writing to the same tables the finance layer reads.

  • Multi-tender billing on 80mm receipts: cash, card, UPI and credit in one sale
  • Live stock on hand across every store and warehouse
  • Inter-location transfers, sell-returns and credit notes
  • Returning customers recognised at the counter, with lifetime value
  • Day-end reports, consignment settlement views and GST Rule 32(5)
  • Role-based access for cashier, manager and admin
inventory

Barcoding and counts

Barcode-first stock control as a scanner PWA on the phone the store already has.

  • Scan to receive, scan to transfer, scan to count
  • Reconciliation that runs itself instead of waiting for a stock take
  • Dead SKUs, missing fields and broken variants found before buyers do
  • Stock ageing that the working capital view can actually use
oms and qr

Custom OMS, and live stock on the shelf

Online and offline demand against one pool of stock, and a shelf a shopper can interrogate.

  • Storefront and marketplace orders in one queue, allocated by your rule
  • Exchanges and RTO handled in the flow rather than over email
  • Scan the shelf QR to see live sizes in this store, right now
  • A linked view opens at the counter, so the cashier sees the same thing
Layer 03Storefront and tools · the rest of the stack

The storefront, the tools and the negotiations around it.

One studio for the technical work a brand rarely has in house. This is also usually the easiest place to start: a Shopify build is a short, visible project, and it puts the studio inside the stack where the finance work happens.

shopify and web

Shopify and custom storefronts

Shopify themes and apps, headless storefronts and interactive launches, built to load on an ordinary phone.

  • Shopify builds, migrations, theme work and custom apps
  • Checkout, shipping and COD logic that matches your actual policy
  • 3D product pages and interactive launches where they earn their weight
  • Order Health runs thirty-four checks on any storefront, free
tools

Internal tools and dashboards

One screen for ops, approvals and numbers, with roles per person and an audit trail behind it.

  • The founder view: sales, stock, cash and ageing in one place
  • Approval flows that replace a chat group
  • Support triage sorting every ticket P1 to P3 by rule
  • Reporting your team can run without calling you
automation and partners

Workflow automation and negotiation

The weekly grind connected up, and the rate conversations run on your own numbers.

  • Sheets, CRM, messaging, email, Shopify and accounting, connected
  • Content engines for reels and listings, each one human-approved
  • Couriers, marketplaces, payment providers and suppliers, renegotiated
  • Blended spend visibility a founder can read in one screen
OwnershipCustom and owned, instead of rented

Off-the-shelf software is a good product sold to ten thousand brands at once.

That is exactly the problem. You pay per user, per store and per module, every month, forever, and your process bends to fit the software. The awkward parts become manual workarounds in a spreadsheet, which is where the leaks start. A custom system bends the other way.

 
Software you rent
A system built for you
Fit
Your process is reshaped to match the product, and the parts that do not fit move into spreadsheets.
Built around how your brand already sells, counts and settles, including the parts that are unusual.
Cost shape
A licence that recurs per user, per store, per module and per extra company, rising every time you grow.
A build, then an agreed support arrangement. Opening a store does not open a new invoice line.
Ownership
You rent access. Stop paying and you lose the system, and usually the convenient way out of it.
You own the codebase and the database. The data sits in your schema, in your Postgres.
Change requests
A ticket, a queue, a roadmap and a maybe, because your edge case is one of ten thousand.
You talk to the person who wrote it. A change that matters ships in days, not in a release cycle.
Integrations
Whatever the vendor has built a connector for, in the shape the connector allows.
Whatever has an API, plus the ones that do not and need a scraper or a file drop instead.
What you end up with
Software you operate.
An asset on your own balance sheet that a competitor cannot buy off a shelf.
Your repository

The source lives in your organisation. Handover is a real handover, including the schema and the runbook.

Your database

PostgreSQL in your account. Every table readable, every export yours, no gatekeeper on your own history.

Your hosting

Deployed to infrastructure in your name, so the bill and the keys are both yours.

Founder built

One person who understands the operations wrote it, and that same person answers the phone.

How it goesFive stages, in the open

The money first, the software second, and nothing on faith.

You can stop after any stage.

The order is deliberate. The finance work proves itself on your own files before anyone asks you to fund a build, and a system that touches money at the counter runs alongside what you use today before it replaces it.

You get a written scope before anything is built, a system you can break in a test store before it bills a customer, and a cutover plan with a way back.

  1. 01Find. Last month's files, read for leaks, priced in rupees. Free, and the findings are yours either way.
  2. 02Fix. The biggest leaks closed, the renegotiations run on your numbers, the reconciliation put on a schedule.
  3. 03Map. Only if the fix keeps hitting the same wall. We sit at your counter and in your warehouse and write down what actually happens.
  4. 04Build and pilot. Billing, stock and day-end for one store on your real catalogue, run in parallel for a full month end.
  5. 05Roll out and run. Remaining stores and channels, then an agreed support arrangement. The repository is yours throughout.
ProofThirteen systems you can open right now

Not screenshots in a deck. Live, and openable.

The finance systems are the offer. The retail systems are the evidence that the offer gets built properly rather than bodged.

Send me last month's files.

Fifteen minutes. Settlements, ninety days of orders with returns, your courier and gateway rate cards. You get the leaks named and priced whether or not anything else happens. If a build is the wrong answer for you, I will say so on the call.

Book a 15-min call ▸
© 2026 AEVYX · FOUNDED BY AASHISH ARORA · NEW DELHI · WORKING GLOBALLYHELLO@AEVYX.IN · @AEVYX.IN