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.

1

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.

2

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.

3

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.

4

You fulfill the order

The order enters your standard fulfillment workflow in Fulfil, the same as any other sales order.

FAQ

Questions? Answers.

What is an EDI 875?
The 875 is the grocery industry's equivalent of the 850 Purchase Order and is used exclusively in the grocery and food distribution vertical. Retailers and wholesalers such as C&S Wholesale Grocers use the 875 instead of the 850 when sending orders to their vendors. It's inbound only: Fulfil receives the 875 and creates a sales order from it the same way it processes an 850.
What information does an 875 include?
The 875 carries the same core fields as an 850: the purchase order number, order date and requested delivery dates, and payment terms and currency. On the product side it includes SKUs and UPCs, quantities ordered per item, unit prices and totals, and the ship-to address.
How does Fulfil process an incoming 875?
The 875 is processed by Fulfil's Native EDI parser, so it isn't available through the SPS Commerce or Orderful integrations. Fulfil parses and validates it against the trading partner configuration, then creates a sales order automatically with line items, quantities, and pricing. The document then shows as Accepted in the EDI monitor.
Do I need special setup if I already handle the 850?
No. Fulfil uses the same product identification and order creation logic for the 875 as it does for the 850, so no custom processing rules are required. You add a document configuration for the trading partner with Transaction Type set to Grocery Products Purchase Order (875) and Direction set to Inbound, and the order then flows into your standard fulfillment workflow.
How are products on the 875 matched to my catalog?
Fulfil matches products using the product qualifier configured for that trading partner, which can resolve against the SKU, supplier SKU, buyer SKU, EAN, or UPC. If you set more than one qualifier, Fulfil checks them in order and falls back to the next when one doesn't match. This is the same matching logic used for the 850.
Which EDI documents work with the 875?
The 875 pairs with the 880 Grocery Products Invoice you send back in the grocery workflow. It maps to the standard 850 Purchase Order and 810 Invoice used outside the grocery vertical.

Selling to grocery wholesalers?
Fulfil handles their EDI.