Two intake paths. One clean PO queue.
Whether the PO arrives as a CSV export or as rows pasted off the portal screen, it lands in FilFlo as structured, mapped data with the source preserved.
Export POs from the Instamart portal
Your team downloads the purchase-order CSV from the Swiggy Instamart vendor portal as part of the daily PO routine — the file is the source of truth for what Instamart ordered.
Import the CSV into FilFlo
The PO header and lines are captured on import, with the source file preserved against the order — any line can be traced back to what the portal actually said.
Mapping resolves the details
Platform SKU codes are matched to your catalog through FilFlo's SKU mapping, and the PO resolves to the mapped buyer entity, GSTIN and delivery location.
The PO joins the approval queue
The Instamart PO sits in the same queue as every other channel, ready for SKU-level approval with quantity cuts, reasons and crate-MOQ rules.
Copy PO rows from the portal
No file download needed — copy the purchase-order rows straight off the Instamart portal screen, exactly as they appear.
Paste into the PO Tracker
FilFlo's PO Tracker workspace has paste-from-portal intake built in: pasted rows are parsed into structured PO data on the spot.
Normalization runs at intake
Portal dates that arrive without a year — DD-MMM formats like “14-Aug” — are resolved into full calendar dates, and platform SKU codes are matched to your catalog.
Exceptions surfaced at intake
The intake is designed to surface unmapped SKU codes and unparseable dates at paste time, before approval — catching portal formatting quirks before they reach an invoice.
Paste from the portal. Get a clean PO.
Portal data is written for a screen, not for a system. Dates come through without a year — DD-MMM formats like “14-Aug” — and line items carry Instamart's own SKU codes rather than yours. FilFlo's PO Tracker normalizes both at paste time: dates are resolved into full calendar dates, and platform SKU codes are matched to your catalog through SKU mapping. The flow is designed to surface unmapped SKU codes and unparseable dates at intake, before approval — catching formatting quirks before they become approval, invoice or appointment errors.
What crosses the wire.
PO number, buyer details, line quantities and rates captured from the CSV or the pasted portal rows — with the source document preserved against the order.
Pasted portal dates — including yearless DD-MMM formats — are normalized into full calendar dates in the PO Tracker, so appointment tracking works on real dates.
Instamart item codes are mapped to your FilFlo catalog through SKU mapping, so every PO line lands on the right product, case size and rate card.
Incoming POs resolve to the mapped customer, GSTIN and delivery location, so approval and GST invoicing run against the right records from the start.
What the workflow enforces — and what it expects.
Source document preserved
The original CSV or pasted payload is kept against the order. When a quantity or rate is questioned later, the team can see exactly what the portal said at intake.
Normalize first, approve second
Pasted portal dates are normalized in the PO Tracker and SKU codes are mapped before the PO reaches SKU-level approval — designed to stop portal formatting quirks from turning into invoice or appointment errors downstream.
Team-initiated intake
Nothing enters FilFlo without a person importing or pasting it. There is no background connection reading data from Instamart's systems on its own.
File workflow, not a system connection
Instamart POs arrive when your team imports a CSV or pastes from the portal. Build intake into the daily portal routine — FilFlo does not fetch Instamart POs by itself.
No consumer-level Instamart data
FilFlo works with the purchase orders Instamart raises on your brand. It has no visibility into consumer orders, dark-store demand or shopper analytics inside Instamart.
Frequently asked questions.
How do Swiggy Instamart POs get into FilFlo?
Two ways, both file-based. Your team can import the purchase-order CSV downloaded from the Instamart vendor portal, or copy PO rows off the portal screen and paste them straight into FilFlo's PO Tracker. Either way, the PO header and lines are captured with the source document preserved, and the order joins the same approval queue as POs from every other channel — webhook, email or file.
How does paste-intake avoid date and SKU errors?
The PO Tracker normalizes pasted portal data at intake. Portal dates that arrive without a year — DD-MMM formats like “14-Aug” — are resolved into full calendar dates, and platform SKU codes are matched to your catalog through FilFlo's SKU mapping. The intake is designed to surface unmapped SKU codes and unparseable dates at paste time, before approval — instead of them being discovered on an invoice or at a delivery appointment.
Is this a direct connection to Swiggy Instamart's systems?
No — and this page doesn't claim one. The Instamart workflow is file-based: POs enter FilFlo when your team imports a CSV or pastes from the portal, and nothing runs in the background against Instamart's systems. FilFlo is an independent product with no partnership or endorsement from Swiggy. What the workflow does mean is that once a PO is in, it gets the same treatment as any other channel — normalized data, SKU-level approval and a reconciliation-ready event trail.
What happens after an Instamart PO is in FilFlo?
The same order-to-cash flow as every other PO-driven channel. The PO gets SKU-level approval with quantity cuts, reasons and crate-MOQ rules; picklists with batch, expiry and FIFO-aware allocation; GST invoicing with IRN and e-way bills against the right entity and series; and GRN capture with invoice-vs-GRN variance classified with reasons. The PO Tracker keeps appointment status and crate/box utilisation visible, with Excel export for the team — and approved orders can feed ERP, live today with Microsoft Dynamics 365, with Tally and Zoho Books export formats available.
Watch a pasted Instamart PO become a clean order.
Book a 30-minute demo and see the full loop: PO rows pasted from the portal, dates and SKU codes normalized in the PO Tracker, SKU-level approval with crate-MOQ rules, and a GST invoice raised against the right entity.