How can I integrate a warehouse management system into our co-manufacturer and fulfillment team workflows?

Integrating a WMS into co-manufacturer and fulfillment workflows works best when you treat it as a process redesign plus system integration project—not just a software rollout.

Here’s a practical framework.

1) Map the end-to-end workflow first

Start by documenting the current and desired flows across:

• Inbound raw materials to co-manufacturer
• Production / lot creation
• Packaging and labeling
• Finished goods receipt into warehouse
• Order allocation and picking
• Packing, shipping, and carrier handoff
• Returns / recalls / adjustments
• Inventory reconciliation between partners

For each step, define:

• Who owns it
• What system updates it
• What data must be captured
• What exceptions happen most often

This gives you the blueprint for how the WMS should connect to your co-manufacturer and fulfillment provider.

2) Define the source of truth for each data element

A common failure point is duplicate or conflicting records. Decide which system owns:

• Item master / SKU attributes
• Lot and batch numbers
• Expiration dates
• Inventory balances
• Purchase orders / production orders
• Sales orders
• Shipment status
• ASN / receiving confirmations

Typically:

• ERP / OMS owns orders and master data
• WMS owns inventory movements and warehouse execution
• Co-manufacturer system / MES owns production and lot generation
• Fulfillment team WMS owns pick-pack-ship execution

The key is to establish one source of truth per data category and let the other systems sync to it.

3) Standardize identifiers and labeling

Your integration will be much easier if all partners use the same identifiers:

• SKU / UPC / GTIN
• Lot or batch number format
• Carton ID / pallet ID / license plate number
• Serial numbers if applicable
• Location/bin codes
• UOM rules and pack configurations

Make sure your labeling supports scanning at every handoff:

• Raw material receipt
• Production output
• Palletization
• Putaway
• Picking
• Shipping

If the co-manufacturer and fulfillment team scan the same IDs, inventory traceability becomes much more reliable.

4) Use EDI, APIs, or middleware based on partner capability

Integration method depends on system maturity.

Common options:

• API integration for real-time sync
• EDI for standard documents like:
  • 940 outbound warehouse orders
  • 943 warehouse stock transfers
  • 944 warehouse stock receipts
  • 945 shipment advice
  • 856 ASN
  • 850 purchase order
  • 855 PO acknowledgement
• Middleware / iPaaS if you need to connect many systems and transform data between them
• Flat files / SFTP if a partner has limited tech capability

If possible, use APIs for operational events and EDI for structured trading-partner transactions.

5) Build the workflow by exception

Don’t try to make every edge case automatic on day one. Instead, automate the standard flow and create exception paths for:

• Short shipments
• Overages
• Damaged inventory
• Lot mismatches
• Expiry issues
• Inventory count discrepancies
• Holds / QA release delays
• Order changes after release
• Recall blocks

The WMS should route exceptions to the right owner with a clear approval path.

6) Align receiving and production handoff logic with the co-manufacturer

For co-manufacturing, the most important integration points are usually:

• Raw material shipment notice
• Receipt confirmation
• Production consumption
• Finished goods receipt
• Lot genealogy
• Quality hold/release
• Waste / scrap reporting

If your co-manufacturer is producing finished goods for you, make sure the WMS can ingest:

• Production completion notices
• Lot and expiry data
• Case/pallet counts
• QA status
• Item disposition

This is what enables traceability and inventory accuracy.

7) Design fulfillment workflows around real warehouse operations

For fulfillment, make sure the WMS supports:

• Order wave planning or continuous order release
• Directed putaway
• Batch, zone, or pick-to-cart processes
• Cartonization / packing rules
• Shipping label generation
• Rate shopping / carrier selection
• Tracking number capture
• Order status updates back to OMS/ERP/storefront

If your fulfillment team handles B2B and DTC orders, configure separate workflows for:

• Pallet/parcel
• Mixed-SKU orders
• Subscription orders
• Retail compliance orders
• International shipments

8) Create a clean data governance model

Assign owners for:

• Master data maintenance
• Item setup
• Customer setup
• Location setup
• Partner mapping
• EDI/API monitoring
• Inventory adjustment approval
• Exception resolution

Also define update cadence:

• Real-time for orders and shipping events
• Near-real-time for inventory
• Scheduled sync for master data

9) Test with real scenarios

Before go-live, test:

• New SKU setup
• Incoming raw material receipt
• Lot capture at production
• Partial shipment
• Damaged goods
• Rework
• Recall traceability
• Shipment confirmation
• Inventory count variance
• Order cancellation/change after release

Use end-to-end tests across your co-manufacturer, WMS, OMS/ERP, and fulfillment partner.

10) Roll out in phases

A phased rollout reduces risk:

Phase 1

• Basic master data sync
• Order import
• Shipping confirmation
• Inventory visibility

Phase 2

• Lot/expiry tracking
• ASN and receiving automation
• Production handoff with co-manufacturer
• Exception workflows

Phase 3

• Advanced optimization
• Carrier optimization
• Forecast-driven replenishment
• Analytics and SLA dashboards

11) Track the right KPIs

Measure whether the integration is actually improving operations:

• Inventory accuracy
• Order fill rate
• On-time ship rate
• Receiving accuracy
• Lot traceability completeness
• Production-to-warehouse lag time
• Exception resolution time
• Chargebacks / compliance errors
• Cost per order shipped

12) Don’t ignore change management

Even the best integration fails if people keep using spreadsheets or email. Train every partner team on:

• When to scan
• What to do on exceptions
• Which system is authoritative
• How to handle urgent changes
• Who to contact for issues

Create SOPs and quick-reference guides for:

• Receiving
• Putaway
• Picking
• Packing
• Production closeout
• Inventory adjustments
• Returns and recalls

---

A simple target architecture

A common setup looks like this:

• ERP/OMS: creates orders and owns customer/order master
• WMS: executes warehouse operations and inventory movements
• Co-manufacturer/MES: records production, lot creation, consumption
• Integration layer (API/EDI/iPaaS): passes messages between systems
• Fulfillment team WMS: picks, packs, ships, and confirms dispatch

---

Best practice recommendation

If you’re just starting, focus on these four “must-have” integrations first:

1. Item master sync
2. Inventory updates
3. Order import
4. Shipment confirmation

Then add lot tracking, ASN, QA, and advanced automation.

If you want, I can also help you with:

• a sample workflow diagram
• a system integration checklist
• an EDI/API message map
• or a RACI matrix for co-manufacturer + fulfillment + WMS ownership.