Why didn’t a retailer’s EDI purchase order come into Endless correctly, and how do I fix it?

A missing or incomplete EDI order usually means the PO has not reached Endless EDI yet, a line did not match a product, or the line’s unit has no mapping.

Endless checks for new purchase orders every 5 minutes and creates a Pending sales order for each. If one is missing, use Import from integration on the Orders page: choose the Endless EDI integration, enter the PO number exactly as on the retailer’s PO, and select Find. The result shows Already in Endless or Not in Endless, and you can import it. If nothing is found, the PO has not reached Endless EDI; ask the retailer to resend it.

Endless matches each line to a product by SKU first, then by the product’s external identifiers for that customer or integration, then by UPC. A line that matches nothing comes in without a product, the activity shows “No product found for …”, and the order cannot be fulfilled until you fix the line.

“Could not resolve the unit of measure” means the line’s unit code has no mapping, or the product lacks a pack quantity for the mapped level. Endless places the order on hold. On the integration’s Data mapping tab, under Unit of Measure Mappings, select Add mapping, enter the retailer’s UOM Code, such as CA, and choose a Packout Level: Each, Inner Pack, Master Carton, Pallet, or Custom Attribute. The product needs that pack quantity in its packout data. The held order keeps the retailer’s quantity, so correct the line to eaches and release the hold.

Many retailers send only a store or distribution center code. Endless looks it up in the retailer’s address list, which Endless loads during setup. A code missing from that list leaves the order without a ship-to address. Enter the address on the order, and contact Endless support to add the location.

A SKU change does not break matching while the UPC is unchanged: when the SKU on the PO matches nothing, Endless falls back to the UPC.