EDI Document
875 Grocery Products Purchase Order.
Same as an 850, built for grocery.
Retailers and wholesalers like C&S Wholesale Grocers use the 875 instead of the 850 when placing orders with grocery vendors. Fulfil processes them the same way, automatically creating a sales order with no manual entry.
What's included in an 875.
The 875 carries the same core fields as an 850 Purchase Order. If you've set up 850 processing, the 875 will feel familiar.
Order Details
- ✓ Purchase order number
- ✓ Order date and requested delivery dates
- ✓ Payment terms and currency
Product & Shipping
- ✓ Product SKUs and UPCs
- ✓ Quantities ordered per item
- ✓ Unit prices and totals
- ✓ Ship-to address
How 875 works in Fulfil.
Fulfil processes the 875 using the same product identification and order creation logic as the 850. No custom processing rules are required.
Grocery wholesaler sends 875
When a grocery wholesaler or retailer places an order, their system sends an 875 to Fulfil through your Native EDI connection.
Fulfil parses and validates
The 875 is parsed and validated against the trading partner configuration. Products are matched using the identifiers configured for that partner.
Sales order created automatically
A sales order is created with line items, quantities, and pricing from the 875. The document status shows as Accepted in the EDI monitor.
You fulfill the order
The order enters your standard fulfillment workflow in Fulfil, the same as any other sales order.
Related EDI documents.
The 875 works with the 880 Grocery Products Invoice in the grocery EDI workflow.