MULTI-CARRIER SHIPPING OS · IN / EU / US
Most shipping platforms are built on the rate card. MARG is built on the one thing they guess at — the parcel itself. Allocated, scanned out, signed for, and accounted for.
The screen goes red and the van waits. That parcel does not leave.
ONE PARCEL · FIVE HAND-OFFS · ONE RECORD
Nothing here was typed. Every line is a scan MARG received and kept.
THE GAP EVERY OPERATOR LIVES IN
01 — THE DOOR
Nobody can say which parcels physically left today. The manifest is a printout someone ticked, or nothing at all.
02 — THE PROMISE
A courier misses its own committed TAT and nobody claims it, because the evidence was never assembled while it was still true.
03 — THE BILL
The invoice arrives weighted higher than the parcel was. Disputing it means proving a number you never recorded.
So MARG starts where the loss starts — at the parcel. Here is the whole path, in order.
ACT I
Shopify syncs continuously — not on a nightly cron. Orders paginate to a thousand at a time, so a flash sale doesn't quietly truncate your day. Nothing is retyped, which means nothing is mistyped.
Every order is read for the signals that predict an RTO: keyboard-mashed names, addresses too short to deliver to, repeat refusers. High risk is a flag on the order, not a report you read next month.
| Address | Signal | Verdict |
|---|---|---|
| 14/2 Kamaraj Salai, T. Nagar, Chennai 600017 | complete | CLEAR |
| near bus stand | 14 chars, no pin | HIGH RISK |
| asdfgh jkl, 110001 | keyboard-mash | HIGH RISK |
ACT II
MARG prices every order against your own rate cards — zone, weight slab, volumetric, COD fee, fuel — and picks the courier by rule, not by habit. If it cannot price an order, it refuses to allocate it. A refusal is cheap. A parcel booked at a rate you never agreed to is not.
| Courier | Price | Days | State |
|---|---|---|---|
| Ekart | ₹64.20 | 3.1 d | ALLOCATED |
| Delhivery | ₹67.00 | 2.8 d | priced |
| Xpressbees | ₹61.80 | 4.4 d | priced |
| Bluedart | — | — | NOT SERVICEABLE |
Thermal and A4, your logo, Code 128 with the human-readable string always printed underneath. Print a filtered run — one courier, one pickup slot, one shelf — instead of everything and then sorting by hand.
ACT III — THE PART NOBODY ELSE BUILT
Every platform in this category books a label. This is the step they skip — and it is the only one that turns a database row into a fact.
A parcel leaves by being scanned out. Not ticked, not assumed — scanned. If the code isn't on today's manifest for that courier, the screen goes full-screen red and the van waits. The stop is the product.
SCAN ANY ORDER
AWB or order id, handheld or phone camera. No pre-selection, no queue to build first.
FULL-SCREEN STOP
Wrong courier, wrong day, already dispatched, cancelled after packing — all one loud red.
TIMESTAMPED, BY WHOM
Every scan carries the operator and the second. That is your chain of custody.
One sheet per courier per handover, generated from what was actually scanned — never from what was planned. The rider signs it. Forty-five days of them stay retrievable, which is exactly as long as an argument about a missing parcel takes to arrive.
39
parcels on the sheet — the count the rider signs for, not the count you hoped to send
2
held back, with the reason recorded against each order
45 d
of signed handover history, searchable by AWB, courier or date
ACT IV
Carrier webhooks come in raw and are archived exactly as sent. Codes MARG doesn't recognise go to a review queue instead of being silently mapped to "in transit". And if a courier's feed goes quiet, an alarm fires — because silence is the most expensive status there is.
RAW SCANS ARCHIVED
The courier's own words, kept verbatim. When they dispute a timeline, you have their payload.
UNKNOWN CODE → REVIEW
A status MARG can't interpret is surfaced, not guessed. Mappings are yours to confirm.
FEED-HEALTH ALARMS
No scans from a courier in N hours is itself an event, routed to whoever owns that lane.
Your logo, your colours, your domain — a public tracking page that reads the same record your ops team does. Alerts go out on the channels the buyer actually opens, and they say what happened rather than apologising for the courier.
YOUR BRAND · PUBLIC PAGE
Out for delivery
Expected today, before 8pm
BUYER ALERT · WHATSAPP
Your parcel left our warehouse at 6:41pm. Ekart has it, and it should reach you by Friday. Track it here.
BUYER ALERT · DELIVERY FAILED
The rider couldn't reach you today. Confirm your address or pick a new date — one tap, no phone call.
Fewer "where is my order" tickets is a side effect, not the pitch. The pitch is that the buyer and your ops team read one record.
A failed delivery has a short life before it becomes a return trip you pay for twice. MARG triages it: the buyer is asked on WhatsApp with buttons, their answer is filed with the courier where the courier accepts one — and flagged for a person where it does not. Every action is logged against the parcel, so the second failure isn't a mystery.
| Parcel | Courier reason | Action taken |
|---|---|---|
| SRTP0034291847 | customer unavailable | RE-ATTEMPT SET |
| DL2290117744 | address incomplete | BUYER CONFIRMED |
| XB88120045519 | refused at door | RTO ACCEPTED |
A return comes back through the same gate it left: scanned in, matched to the original parcel, condition recorded. Return insights then tell you the thing nobody wants to look at — which SKU, which pin code, which courier, which size, keeps coming back.
ACT V
Every courier commits to a TAT. MARG holds them to their own number: parcels past promise are listed with the scan history, the manifest, and the signature already attached. A TAT claim stops being a favour you ask and becomes a file you send.
| AWB | Promised | Elapsed | Claim |
|---|---|---|---|
| DL2290117744 | 3.0 d | 6.2 d | FILED |
| XB88120045512 | 4.0 d | 9.4 d | EVIDENCE READY |
| SRTP0034291799 | 3.0 d | 5.1 d | CREDITED |
The weight that matters is the one captured at your bench, at scan-out, against that parcel. When a courier invoices a heavier number, the dispute is a comparison — not a conversation about what you think you sent.
YOURS AT SCAN-OUT
1.240 KG
ON THE INVOICE
2.500 KG
DISPUTE, WITH EVIDENCE
Bench weight, scan timestamp, operator, manifest line — one click, one file.
Billing lines up freight, COD remittance and claims against the orders in your store. Anything that doesn't match — a parcel billed twice, a COD never remitted, an order shipped that no longer exists — sits in an exceptions list rather than in your margin.
FREIGHT vs RATE CARD
Each line checked against the card you actually signed, zone by zone.
COD REMITTANCE
Delivered and collected, matched to money received and the date it landed.
EXCEPTIONS, NAMED
Double-billed, short-paid, phantom shipment — each with the record that proves it.
Sixteen panels on one filter set, refreshing every sixty seconds. Courier scorecards, lane performance, RTO by pin code, promise adherence, weight variance. Every panel exports, because the number that changes a contract has to leave the tool.
EXAMPLE DATA Figures below illustrate the panel, and are not a customer's numbers.
ON-TIME
94.2%
RTO RATE
6.8%
WT VARIANCE
+0.31
NDR RECOVERED
71%
CLAIMS FILED
128
THE COURIERS
Each courier is an adapter with three jobs — book, track, resolve NDR — and MARG shows you which of the three is live. Where an adapter isn't built, the console says so on the courier's own row. Adding a carrier is an adapter, not a rewrite, which is how the same platform runs an Indian pin code and a German postcode.
| Carrier | Adapter | State |
|---|---|---|
| Delhivery | BOOK TRACK NDR | READY |
| Xpressbees | BOOK TRACK NDR | BOOK & TRACK |
| Bluedart | BOOK TRACK NDR | TRACKING ONLY |
| Ekart | BOOK TRACK NDR | BOOK & TRACK |
| Porter | BOOK TRACK NDR | RIDERS · NOT YET LIVE |
NDR means MARG can file a re-attempt, a deferral or an address correction with the courier over their API. Where it is unlit, a failed delivery is still captured and triaged — the instruction goes to the courier by hand.
India — Delhivery, Xpressbees, Bluedart, Ekart, your own contracts, and Porter riders across town — built to their published API, not yet run against a live key.
Europe & USA — carrier adapters on the same three-job contract.
WHAT IT PLUGS INTO
MARG doesn't ask you to move your store, your contracts or your finance stack. It sits between them and keeps the parcel's record whole.
STORES
Shopify, live
Continuous sync, pagination to 1,000, no nightly cron. WooCommerce and custom carts on the same contract.
CARRIERS
Book · track · NDR
Each carrier is an adapter with three jobs. The console shows which of the three is live, per courier.
API
Webhooks both ways
Push orders in, receive every scan out. Raw payloads archived exactly as the carrier sent them.
WAREHOUSE
Scanners and thermal printers
Any handheld or phone camera at the gate. 4×6 thermal and A4 from the same label spec.
BUYER CHANNELS
WhatsApp, SMS, email
Alerts on the channel the buyer actually opens, on your domain and your brand.
FINANCE
Invoices, COD, claims
Freight checked against your rate card, COD matched to money received, exceptions named.
WHO IT'S FOR
D2C, SCALING
Past 300 parcels a day
The point where a spreadsheet stops being a record and starts being a liability.
MULTI-WAREHOUSE
Two or more doors
Each door scans out against its own manifest, and the numbers still add up at head office.
3PL / FULFILMENT
Shipping for other brands
Your client's proof of dispatch is your invoice defence. Manifests carry both names.
CROSS-BORDER
India, Europe, USA
Different pin codes, currencies and paperwork — one chain of custody behind all of them.
THE DIFFERENCE, PLAINLY
| The question | The usual aggregator | MARG |
|---|---|---|
| Where does it start? | At the rate card | At the parcel |
| Can anything stop a parcel leaving? | No — a label is a label | Yes. Wrong parcel, red screen, van waits |
| What does the handover produce? | A pickup request | A signed manifest, kept 45 days |
| Who owns the weight? | The invoice does | Your bench, at scan-out |
| What happens to a missed TAT? | You notice, eventually | A claim file, evidence attached |
| An unknown carrier status code? | Mapped to "in transit" | Sent to a review queue |
| Can you take the data out? | Some of it, some of the time | Every panel, every manifest |
WHO HOLDS THE RECORD
The packer scans. The supervisor holds parcels back. Finance sees the bill. Admin sees everything, and every change carries a name.
Scans and statuses are added, never overwritten. A corrected record shows the correction — that is the point of it.
Every panel and every manifest exports. Retention is stated on the tracking page, which is what GDPR asks and what buyers deserve.
Ask a question about your own operation in plain language — "which lane broke promise most this week" — and get the panel, not a paragraph.
PRICING
You keep your own courier contracts and your own rates — MARG never sits in the middle of the freight. You pay for the record, and only for parcels that actually left.
BENCH
₹1.90/ parcel scanned out
₹1.40/ parcel scanned out
ESTATE
Talk to us
A parcel that never left the building is never billed. EUR and USD pricing on request.
THE QUESTIONS WE ACTUALLY GET
No. Bring your own accounts and your own negotiated rates — MARG prices against the cards you already signed. We never resell freight, which is why allocation has no reason to favour one courier.
The console says so on that courier's own row, and it will refuse to book rather than pretend. Tracking-only adapters still feed the record. New adapters are built to the same three-job contract: book, track, resolve NDR.
Any handheld barcode scanner works, and so does a phone camera. The gate is a screen and a scan — the investment is the discipline, not the hardware.
Store sync and label printing on day one. The gate goes live once your rate cards and pickup slots are in, which is usually the same week. Nothing needs a migration.
Scans and manifests are append-only and retained 45 days by default, longer on Estate. Retention is stated on the buyer-facing tracking page, and every panel and manifest exports on demand — including on the way out.
Only if you want them to. Labels, the tracking page and every alert carry your logo, your colours and your domain. On the buyer's side MARG is infrastructure, not a brand.
Bring one warehouse day. We'll run it through MARG — sync, allocate, print, scan out, manifest, sign — and you'll see exactly what your current stack cannot tell you.