B2B Fulfillment Services: How to Choose the Right 3PL

TL;DR: Choose a B2B fulfillment service that can prove it will execute your buyers' actual order contract—not merely store and ship inventory. Test purchase-order intake, EDI documents, units of measure, case and pallet builds, labels, routing guides, appointments, pricing, and exception ownership with representative orders before signing or cutting over. A low headline pick fee cannot compensate for failed buyer compliance.

Last updated: August 2026

Last reviewed: August 2026

The short answer: choose against six acceptance gates

A strong B2B fulfillment partner fits the trading relationships you already have or intend to win. The decision should follow six gates in order—define the order contract; test order and EDI intake; test physical execution; normalise price and terms; define service levels and exception owners; then run a controlled pilot—and reject a provider when a critical buyer requirement remains a sales promise instead of a demonstrated workflow.

Acceptance gate	Proof to request	Fail condition
1. Order contract	Buyer, company-location, SKU, unit-of-measure, routing and service requirements mapped in writing	A required field or rule has no system or accountable owner
2. Order and EDI intake	Representative purchase order enters once, is acknowledged, and produces the required shipment notice and invoice events	Staff must re-key ordinary orders or reconcile unnamed document gaps
3. Physical execution	Correct case, pallet, label, pack list, carrier, appointment and proof-of-shipment output	The test fails a buyer routing guide or unit-of-measure rule
4. Commercial model	One priced scenario covering receiving, storage, picks, projects, freight, technology, minimums and exits	A material fee or assumption cannot be modelled from the quote
5. SLA and exceptions	Metric definitions, event timestamps, exclusions, escalation owners, evidence and remedies	The provider grades its own work from an undefined report
6. Acceptance pilot	Ordinary and exception orders pass with reconciled inventory, documents, charges and buyer outcomes	Cutover depends on untested mappings or irreversible migration

Which fulfillment model fits?

Model	Best fit	Main tradeoff
In-house	A team that needs direct process control and can operate the facility, systems, labour and compliance	Control comes with fixed capacity, management and execution responsibility
Hybrid	A business that must retain one specialised workflow while outsourcing routine storage or distribution	More handoffs and inventory reconciliation between owners
B2B-capable 3PL	A business that wants outsourced wholesale execution and can specify its buyer requirements	Less direct control, contract dependence and ongoing governance

Decision attributes: Compare fit, limitations, implementation work, total scenario cost, evidence access, exit terms and the next acceptance test. Setup time and time to value are provider- and integration-specific; request a dependency-based plan rather than accepting a universal launch estimate.

1. Define the B2B order contract

The B2B order contract is the full set of commercial, data and physical rules required to accept and fulfil an order for a business buyer. It begins before the warehouse pick and continues through shipment evidence, invoicing, exceptions and reconciliation.

Shopify's current B2B feature guide includes purchase-order numbers, companies and company locations, catalogs, payment terms and other business-order controls. Its company and customer guide shows why “the customer” is too vague: each company location can carry its own addresses, pricing, payment terms, checkout settings and contacts.

Build a requirement register for each sales channel or buyer group:

1. Order source, company location, purchase-order number and approval state.
2. SKU, buyer item number, case pack, inner pack, each, pallet and permitted substitutions.
3. Ship-to location, routing guide, carrier rule, delivery window and appointment process.
4. Carton, pallet, label, pack-list, certificate and shipment-notice requirements.
5. Backorder, split shipment, cancellation, shortage, damage, refusal and return rules.
6. Invoice, payment-term, proof, dispute and reconciliation requirements.

Keep this six-part order in the provider brief, tests and final verdict. If a field changes the warehouse action, label, transport booking, invoice or buyer acceptance, it belongs in the contract even when the storefront does not display it.

2. Test order and EDI intake

Electronic data interchange (EDI) is structured business-document exchange between trading partners. Do not ask only whether a 3PL “supports EDI”; ask which documents, versions, networks, identifiers, acknowledgements, validation rules and exception queues the provider will operate for each buyer.

X12 defines the EDI 850 Purchase Order for purchase-order data and the EDI 856 Ship Notice/Manifest for shipment contents and related shipment detail. The official X12 supply-chain flow places the 850 purchase order, 855 purchase-order acknowledgement, 856 advance ship notice (ASN), 810 invoice and 820 remittance advice in distinct business steps.

Use a real but reversible test order. Confirm the provider receives the buyer and company-location context, preserves the purchase-order number, maps the correct item and unit of measure, acknowledges the order, blocks invalid data, and creates each required downstream event once. Record who owns a rejected document, how the merchant sees it, and how replay avoids a duplicate shipment or invoice.

For Shopify orders, also test whether payment terms and fulfillment events remain consistent through the handoff. Shopify documents B2B payment terms separately from physical fulfillment; the warehouse should not silently turn a commercial term into a shipping assumption.

3. Test case, pallet and label execution

A B2B warehouse test must prove the physical shipment matches the buyer's data. Validate each, inner, case and pallet units of measure; lot or expiry rules where relevant; carton content; pallet configuration; labels; pack lists; carrier instructions; appointments; and proof of shipment.

If a buyer requires a GS1 logistics label, the GS1 Logistic Label Guideline identifies the Serial Shipping Container Code (SSCC) as the single mandatory element on that label and describes its GS1-128 barcode representation. That does not mean every B2B shipment needs a GS1 label; it means the provider must reproduce the exact standard and buyer rule when it applies.

Run at least one ordinary order and one difficult order from the requirement register. A useful difficult order might contain mixed cases, a partial allocation, a buyer-specific label, an appointment or a backorder. Compare the physical carton and pallet to the order, ASN, pack list and invoice inputs. Photograph or scan the labels and retain the system event trail so a pass is reproducible.

Ask where value-added work happens and what prevents an unapproved substitution. Kitting, relabelling, quality checks and retail preparation can be valid services, but each needs an instruction source, inventory movement, quality evidence, fee and exception owner.

4. Normalise price and commercial terms

Compare providers with one operating scenario, not one headline fee. Supply the same inbound profile, storage mix, order lines, case and pallet activity, projects, returns, peak assumptions, freight scope and technology needs to every bidder; mark an item “not applicable” only when the requirement register proves it is genuinely absent.

Cost family	Normalisation question	Risk to expose
Receiving	What unit, labour rule and discrepancy work is priced?	Hourly work or minimums hidden behind a pallet rate
Storage	How are pallets, bins, cubic space, ageing and peak inventory measured?	A snapshot, daily measure and monthly charge treated as interchangeable
Handling	Which each, case, pallet, label, insert and project touches are separate?	The “pick fee” omits ordinary B2B work
Freight and accessorials	Who books, audits and passes through transport, appointments and corrections?	Unclear markups or buyer non-compliance costs
Technology and support	Which integration, EDI, portal, account and change fees apply?	A required connection appears only after selection
Minimums and exit	What happens below volume, during peak, at renewal and at termination?	Stranded inventory, data or transition work

For a deeper line-item method, use the related guide to 3PL pricing transparency. Keep currency, period and quantity explicit. Do not multiply a rolling monthly snapshot as if it were a daily increment, and do not invent anonymous-provider prices to make a table look complete.

5. Write the SLA and exception ownership

A service-level agreement (SLA) is useful only when the metric, start event, stop event, exclusions, evidence source, reporting grain, review owner and consequence are explicit. “On time” can describe order acknowledgement, pick completion, carrier handoff or buyer delivery; choose the event that the provider actually controls and that the buyer requirement needs.

SLA component	Question to settle
Definition	What exact event qualifies, and in which time zone and business calendar?
Denominator	One row per order, line, unit, shipment, pallet, document or buyer appointment?
Exclusions	Which holds or merchant changes are excluded, and who approves the exclusion?
Evidence	Which source timestamp or document decides a dispute?
Escalation	Who investigates, communicates, corrects and prevents recurrence?
Remedy	What service credit, corrective plan or exit right follows a confirmed miss?

Name owners for order rejection, inventory shortage, damaged stock, label failure, missed appointment, ASN mismatch, invoice dispute, security incident and system outage. The merchant retains responsibility for deciding its customer and buyer commitments; the 3PL owns only the contracted execution and evidence. A software dashboard can surface an issue but cannot replace those operating owners.

6. Run a controlled acceptance pilot

An acceptance pilot is a bounded test of the configured service before full production volume moves. It should include ordinary orders, known exceptions and a written rollback path; a sales demonstration is not an acceptance test because it does not use your mappings, inventory, labels, documents, charges and owners.

1. Freeze the approved requirement register, sample orders and expected outputs.
2. Load a reconciled, limited inventory set and preserve the starting record.
3. Run the six acceptance gates in the same order used in the selection matrix.
4. Reconcile orders, inventory, labels, EDI events, freight, fees and exceptions.
5. Record each defect, owner, correction and retest; do not waive a critical buyer requirement verbally.
6. Approve staged cutover only after required tests pass and rollback remains possible.

The setup plan should name dependencies rather than promise a fixed launch date. Catalog quality, buyer mappings, EDI testing, inventory transfer, facility readiness and exception design determine the schedule. If a provider cannot show the critical path and the owner of each dependency, implementation risk remains unpriced.

Where Forthmatch fits after selection

Disclosure: Forthmatch is our app. It is a free, Shopify-specific tool used to monitor an existing 3PL; the current Shopify App Store listing describes monitoring fulfillment performance, on-time rates and SLA violations.

• Fit: a Shopify merchant wants an independent operating view of an existing 3PL's fulfillment speed, SLA compliance, damage rate and on-time shipping.
• Limitations: Forthmatch does not find, rank, verify, or match providers; it does not generate RFPs or send quote requests; and it is not a warehouse, carrier, WMS or EDI network.
• Price: the software is currently listed as Free.
• Setup: connect the Shopify store, define the monitored commitments and verify the source events before using a dashboard in an accountability review.
• Time to value: No fixed setup time or performance lift is promised; usefulness depends on integration data, agreed definitions and the merchant's review process.
• Alternatives: alternatives include the 3PL's own reporting, a merchant-built report, a warehouse or order-management analytics layer, or a specialist audit.
• Next step: select and contract the provider through the acceptance gates, then decide whether an independent monitoring layer is needed.

For an example of the post-selection boundary, see the guide to Stord alternatives. Provider selection and provider monitoring are related decisions, but they are not the same product capability.

Verdict: buy demonstrated B2B execution

Choose the fulfillment model and provider that passes the six acceptance gates for your real buyers. In-house control may fit a team prepared to own the operation; a hybrid model may preserve one specialised workflow; a B2B-capable 3PL may fit when outsourced execution, systems and governance are stronger than the internal alternative—but no model wins without evidence.

The decisive proof is not a logo list, a low pick fee or a generic Shopify integration. It is a reconciled trail from company location and purchase order through acknowledgement, case and pallet execution, labels, shipment notice, delivery evidence, invoice inputs, exceptions and charges. Run that trail before cutover, preserve the result, and use the same definitions to govern the relationship afterward.

Frequently asked questions

What is B2B fulfillment?

B2B fulfillment is the storage, processing and shipment of orders from one business to another, such as a brand shipping cases or pallets to a retailer, distributor or commercial buyer. It often adds buyer-specific data, routing, labels, appointments, documents and payment terms to ordinary warehouse work.

How is B2B fulfillment different from DTC fulfillment?

Direct-to-consumer fulfillment usually optimises individual parcels and consumer delivery. B2B fulfillment can require purchase orders, company-location rules, EDI documents, case and pallet units, retailer routing guides, labels, freight appointments and invoice reconciliation. A provider may do both, but the B2B workflow must be tested separately.

Which EDI documents should a B2B 3PL support?

The answer depends on each trading partner. Common X12 steps include the 850 purchase order, 855 acknowledgement, 856 advance ship notice and 810 invoice, but a provider must support the exact document, version, identifiers, validation and exception process your buyers require.

How should I compare B2B fulfillment pricing?

Give each provider the same operating scenario and normalise receiving, storage, each/case/pallet handling, labels, projects, freight, technology, minimums, support and exit work. Treat missing terms as open risks, not zero-cost lines.

Can Forthmatch choose a fulfillment partner for me?

No. Forthmatch monitors an existing 3PL for Shopify merchants. It does not operate a provider directory or matching, verification, RFP or quote-request service.