SAP Business One occupies a particular niche: companies that outgrew accounting software but want SAP discipline without an enterprise project. Those companies sell into big-box, grocery, and distribution programs constantly — which means B1 shops meet EDI early, usually the week a major retailer's vendor packet arrives. Here's how the integration works when EDISQ handles the EDI side and Business One stays the system of record.
Documents in, B1 objects out
The core of the integration is a disciplined correspondence between X12 documents and Business One's sales chain:
- 850 → Sales Order. The retailer's PO is validated against that partner's rules, then created as a B1 sales order — business partner resolved, items cross-referenced from the retailer's identifiers to your item master, ship-to addresses matched, PO number preserved for every downstream reference.
- Sales Order → 855. The acknowledgment flows back from what the order actually says you'll ship, satisfying the response-time clocks most majors run.
- Delivery → 856. Adding the delivery in B1 is the trigger: the connector composes the ASN from the delivery's lines and shipping detail, applies the partner's hierarchy and labeling requirements, and transmits while the truck is still en route.
- A/R Invoice → 810. The invoice you post in B1 leaves as an 810 carrying the references — PO number, shipped quantities — that let it match cleanly at the retailer's payables.
- Warehouse data → 846 for partners that want scheduled availability, common in dropship and distributor programs.
The design principle: every EDI action hangs off something your team already does in B1. Nobody "does EDI" as a task; the documents are exhaust from normal operations.
The unglamorous parts the connector absorbs
X12 syntax is the easy half. The daily work is reference data: a retailer orders with its own item numbers and location codes, B1 thinks in your item codes and business partners, and the cross-reference layer translates every document both directions. Add partner-specific validation — segment rules, timing expectations, required identifiers that differ between an 850 from Home Depot and one from a grocery wholesaler — plus automatic 997 acknowledgment exchange, and you have the workload EDISQ's certified maps exist to carry. When a document would fail a partner's rules, it's caught before transmission, which is when fixing it is still free.
From kickoff to first live order
A B1 integration typically follows five steps: connect EDISQ to your Business One system; enable the trading partner (maps and rules load with it); build item and location cross-references against your master data; run the partner's certification scenarios in the sandbox; cut over with acknowledgment tracking watching the first live cycles. The pattern holds whether the partner is one retailer or a dozen — additional partners reuse the same integration with their own maps layered in, drawn from a directory of 2,200+.
Give the sandbox phase real respect. The scenarios worth replaying aren't the happy path — they're the awkward ones: a partial shipment where the delivery covers half the order, a substituted item, a price that changed between order and invoice. B1 handles all of these routinely; the question the sandbox answers is whether the EDI documents describing them satisfy the partner's validation. Certifying against the messy cases is what makes the first quarter of live trading boring, which is the goal.
The commercial model stays flat as you scale, too. EDISQ bills B1-integrated EDI purely by document count: nothing for the first 25 in a month, then a rate ladder running $0.50 down to $0.10 applied marginally by tier — never retroactively — with zero charges for mapping, setup, or the AS2/SFTP/VAN transport underneath, and live trading on a $100/month Production minimum applied entirely to usage. The SAP Business One integration page covers connector details; the ladder itself is on pricing.
FAQ
Is SAP Business One EDI the same as SAP S/4HANA EDI?
No — Business One is SAP's small-and-midsize ERP with its own object model. The EDI concepts match, but the integration works against B1's sales orders, deliveries, and A/R invoices, not S/4 constructs.
What creates the ASN in a Business One flow?
The delivery document. When the delivery is added in B1, the connector picks it up, assembles the 856 with the partner's required hierarchy and identifiers, and transmits it ahead of the freight.
Can Business One send inventory feeds to partners?
Yes — warehouse quantities from B1 can publish as scheduled 846 documents for dropship partners and distributors that require regular availability updates.