Ad spend in one tool. Stock in another. Marketplace settlements weeks late, minus deductions nobody reconciles. ZERPHIX holds all of it on the same rows — so contribution is computed, not assembled after the fact.
Same month, same SKU, same orders. The right-hand column is the left-hand column with the four lines your reporting stack cannot reach — and it is the only one you can bank.
Most “global” software is one product with a currency switcher. Commerce is not like that: the channels, the tax, the settlement shapes and the return economics are different per country, and a connector list that ignores it tells your customer you have never sold in their market. Pick one and watch the console change.
A module that does not apply to a market is hidden, not locked. “Not applicable here” and “not in your plan” are different sentences, and showing the second when you mean the first is how software reads as foreign.
A marketplace seller API, an EDI document set, a vendor-panel report and a storefront webhook all run the same ingest → normalise → store path: dedupe, tax derivation, fee model, journal, stock. What you watch on the right is what happens on a sale morning.
Five documents, five counterparties, sixty-three days — each allocated on its own basis, because one basis for a mixed shipment misprices half a catalogue. Scroll: this is what converging looks like.
Nothing here is joined after the fact. The number on the dashboard is the number in the report is the number in the ledger.
Contribution first, immediately undercut by what gross margin would have told you. Six figures, a watchdog against your own baseline, and where the revenue went — every one a query on the operational tables, not an overnight extract.
Pick a model, pick measures, pick dimensions. Every measure declares in code what it means and which operational screen it reconciles with, so two people asking the same question get the same number.
Not by ROAS. By the contribution the units actually generated, net of cost of goods, channel fees and returns — with a flag on the rows whose ROAS looks fine and whose economics do not.
Marketplace, storefront, EDI vendor and retail media land in the same orders, the same stock ledger, the same books — each with its fee model and settlement shape already built, and each hidden entirely in markets where it does not exist.
| What you use now | What it does well | What ZERPHIX adds |
|---|---|---|
| An OMS or WMS Channel sync and warehouse suites | Runs the warehouse and the channel sync properly. | Ad spend, contribution, landed cost and the ledger on the same rows the warehouse moved. |
| An analytics layer Profit dashboards on top of your channels | Good margin maths, fast to switch on. | The ability to act — pause the creative, reprice the SKU, raise the replenishment — without leaving the screen. |
| Spreadsheets For landed cost and settlement reconciliation | Nothing. It is a spreadsheet. | A cost that converges as documents arrive, and a claim raised before the window closes. |
Not out of the box. The fee models, settlement formats, report parsers, EDI documents and claim windows are built and tested for 57 channels across 43 markets. The seller-API client for each marketplace — the OAuth app, the credentials, the rate limits — is engineering work we do during implementation. It is the last mile, and we would rather say so than let you find out in week two.
Forty minutes. Bring one settlement report and we will show you the deductions nobody reconciled.