ASNs out before goods arrive. POs in as Zepto issues them.
The ASN is the differentiated half: what FilFlo declares to Zepto is reconciled against Zepto's own PO, line by line, before the truck reaches the dock.
Order fulfilled and invoiced
The Zepto PO is approved at SKU level, picked and dispatched, and the GST invoice is raised — in FilFlo, or read back from ERP where ERP invoices (live today with Microsoft Dynamics 365).
ASN assembled from invoice data
FilFlo compiles the Advance Shipping Notice from the actual invoice — quantities, invoice details and dispatch information — against the specific Zepto PO it fulfils.
ASN submitted before goods arrive
The ASN reaches Zepto ahead of the truck, so the receiving side knows what is on the way before the delivery appointment.
Zepto reconciles ASN against PO
Zepto matches the submitted ASN against its purchase order line by line — declared quantities meet ordered quantities before the goods hit the dock.
Zepto issues a purchase order
FilFlo-operated middleware ingests the PO — header and lines — without anyone re-keying it from a portal.
SKUs and buyer context resolved
Zepto item codes are mapped to your SKUs, and the buyer entity and delivery location are resolved so the order lands against the right customer and warehouse.
PO enters the approval queue
The order joins the same queue as every other channel — SKU-level quantity cuts with reasons, crate-MOQ rules, and the approver on record.
Zepto knows what's coming before the truck does.
An Advance Shipping Notice is dispatch information — the PO being fulfilled, invoice details, and the quantities on the way — submitted to Zepto before the goods arrive. Zepto reconciles the ASN against its purchase order line by line, so receiving expectations are settled before the delivery appointment instead of disputed at the dock. FilFlo assembles the ASN from the actual invoice in the order trail — raised in FilFlo, or read back from ERP — and submits it against the right PO.
What crosses the wire.
Invoice, quantity and dispatch details submitted to Zepto before the goods arrive. Zepto reconciles the ASN against its PO line by line.
Ingested through FilFlo-operated middleware as Zepto issues them — header and line level, with the source document preserved.
Zepto item codes are mapped to FilFlo SKUs per channel, so PO lines resolve to the right products without manual matching.
Buyer GSTIN and delivery-location mapping decide which customer account and fulfilling warehouse each Zepto PO posts against.
What the integration enforces — and what it expects.
The PO stays the commercial anchor
Every ASN is built against the specific Zepto purchase order it fulfils, after an approval with SKU-level cuts and reasons on record — nothing is declared to Zepto that wasn't approved first.
Invoice data gates the ASN
The ASN is assembled from actual invoice data, not estimates. Where ERP raises the invoice, the read-back — live today with Dynamics 365 — supplies it, so what's declared to Zepto matches what was billed.
Middleware-operated intake
FilFlo-operated middleware handles PO ingestion, so Zepto orders enter the same approval queue as every other channel without manual re-keying of headers and lines.
ASN enablement is per-account, not default-on
ASN submission is switched on account by account, not automatically for every Zepto customer. Plan enablement as an onboarding step rather than assuming it ships active.
Invoice data readiness is a prerequisite
The ASN carries invoice details, so invoicing must produce that data at dispatch time — either GST invoicing inside FilFlo, or invoice read-back from your ERP — before ASN submission can start.
Frequently asked questions.
What is a Zepto ASN?
An Advance Shipping Notice is dispatch information submitted to Zepto before the goods arrive — which purchase order is being fulfilled, the invoice details, and the quantities on the way. Zepto reconciles the submitted ASN against its own PO line by line, so receiving expectations are set before the delivery appointment rather than argued about at the dock.
What software do brands use to submit ASNs to Zepto?
FilFlo submits ASNs to Zepto as part of its order-to-cash flow. The Zepto PO is ingested, approved at SKU level, fulfilled and invoiced — and FilFlo assembles the ASN from the actual invoice data and submits it to Zepto before the goods arrive. Because the ASN is built from the same order trail as the PO, the approval and the invoice, what's declared to Zepto matches what was approved and billed.
Is ASN submission on by default?
No. ASN enablement is per-account and depends on invoice data readiness — the invoice details the ASN carries must be available at dispatch time. It is configured as part of onboarding, account by account, rather than shipping active for every Zepto customer.
How do Zepto purchase orders get into FilFlo?
Through FilFlo-operated middleware. POs are ingested as Zepto issues them — header and lines — then Zepto item codes are mapped to your SKUs and the buyer entity and delivery location are resolved. The order enters the same approval queue as every other channel, with SKU-level quantity cuts, crate-MOQ rules and the approver on record.
Where does the ASN's invoice data come from?
From the invoice in the order trail. Brands invoicing in FilFlo raise the GST invoice in the dispatch flow, and the ASN is assembled from it. Brands whose ERP raises the invoice use invoice read-back — live today with Microsoft Dynamics 365 — so the ERP invoice feeds the ASN. Either way, the ASN reflects what was actually billed against the Zepto PO.
Watch an ASN go out against a Zepto PO.
Book a 30-minute demo and see the full loop: the Zepto PO ingested through middleware, approved at SKU level, fulfilled and invoiced — and the ASN assembled from the invoice and submitted to Zepto before the goods arrive.