Fishbowl is where a lot of QuickBooks companies land when the spreadsheet finally breaks: real inventory control, manufacturing work orders, and warehousing, without leaving the QuickBooks universe for a full ERP. Which means Fishbowl shops are exactly the size and shape of company that big retailers love to onboard — and exactly the size that has never run an EDI program. When the first routing guide arrives, here is how the pieces fit.
The three-system reality
A typical Fishbowl stack has three systems with clear jobs: Fishbowl owns items, stock, orders, and shipping; QuickBooks owns the ledger via the Fishbowl sync; and the warehouse floor runs on Fishbowl's picking and shipping workflow. EDI should not disturb that arrangement — it should ride it.
The pattern that works: the EDI layer converts each partner document into the Fishbowl object it corresponds to, and listens for the Fishbowl events that trigger outbound documents. Nothing about your QuickBooks sync changes; the books see EDI orders as ordinary sales.
- Inbound 850 → Fishbowl sales order. The retailer's item numbers and UPCs cross-reference to your Fishbowl part numbers, the ship-to resolves to the right customer and location, and the order drops into your normal pick/pack/ship queue.
- 855 acknowledgment out, confirming what you can ship inside the partner's window — most majors expect it within 24 hours.
- Ship confirm → 856 ASN. The moment Fishbowl confirms the shipment, the ASN transmits with the pack structure the partner requires. GS1-128 carton labels are included free with EDISQ, and the SSCC-18 allocation is shared between the label and the ASN's MAN segments — the mismatch that drives so many chargebacks becomes structurally impossible.
- Invoice → 810, quoting the PO and the as-shipped quantities so the retailer's three-way match clears — while the same transaction flows to QuickBooks through the sync you already trust. If you have read our QuickBooks Online EDI guide, this is the same philosophy with Fishbowl as the operational front end.
- Stock → 846 for dropship programs that want inventory feeds on cadence.
The setup work that matters
Two cross-references carry the whole integration. First, items: retailers order by their item numbers and UPCs; Fishbowl thinks in part numbers. Build the two-way cross-reference once, keep it in one place, and half of compliance follows. Second, locations: big retailers ship to dozens of DCs identified by location codes, and each must resolve to the right Fishbowl customer/ship-to so orders route and ASNs reference correctly.
One warehouse-specific note: retailers grade the 856 on whether it mirrors the physical pack-out. Generate the ASN from Fishbowl's actual pick and pack data — cartons as packed, quantities as shipped — never from the original order. Short-ship a line, and the SN1 says so; the 810 then bills what shipped. Lineage from one shipment record is what keeps labels, ASN, and invoice in agreement.
Going live
Pick your partner from the directory — 2,200+ trading partners with certified maps, from Walmart and Target to the distributors — and the companion-guide rules arrive as configuration. Wire the connector (activated on request; CSV import/export is live from day one, a workable bridge for a Fishbowl shop's first partner). Build the two cross-references. Then test in sandbox until the partner's scenarios pass end to end: order in, 855 back, ASN hierarchy validated, invoice matching.
Adding partner two and three is where the design pays: Fishbowl and QuickBooks never change; each new retailer is a new map set on the EDISQ side.
What it costs
Fishbowl-size companies are precisely who opaque EDI pricing hurts most — a four-figure setup quote can stall a first retail program entirely. EDISQ's meter is published on the pricing page: first 25 documents monthly free, then from $0.50 per document, tapering with volume, with connectivity (AS2, VAN, SFTP), maps, labels, and automatic 997s included. Self-serve signup, no monthly fee on the Self-Serve plan — the retail invitation gets a yes without a budget meeting.
FAQ
Does Fishbowl support EDI out of the box?
Fishbowl focuses on inventory, manufacturing, and warehousing. Retail EDI — partner-specific X12 documents, connectivity, compliance — comes from pairing Fishbowl with an EDI layer that converts documents into Fishbowl orders and reads shipments back out.
How does EDI work alongside the QuickBooks sync?
Fishbowl handles orders and fulfillment; QuickBooks handles the books. EDI orders land in Fishbowl as sales orders, ship confirms drive the 856, and invoicing data flows through the same Fishbowl-to-QuickBooks sync you already run.
Where does the 856 ASN come from?
From Fishbowl's ship confirmation. When the order ships, the connector builds the ASN with the partner's required carton hierarchy and SSCC-18 serials matching the GS1-128 labels, and transmits it before the freight arrives.
What does Fishbowl EDI cost with EDISQ?
Per document: first 25 each month free, then from $0.50 per document, decreasing with volume. Connectivity and maps are included; there is no monthly fee on the Self-Serve plan.