When buyers have different EDI requirements

If you work with more than one retailer, you already know the drill. Each buyer has a specific set of EDI requirements, and those requirements can change over time. That is exactly why Procurant uses a hub-and-spoke model for connectivity.

On the supplier side, there are multiple ways to connect. A supplier might use AS2, a VAN, an API or update orders directly in the Procurant Portal. Some teams even use a mix, depending on what fits their day-to-day workflow.

What stays consistent is what the buyer receives.

Procurant's outbound connection to each retailer is based on that retailer’s compliance rules and document specifications. So no matter how a supplier updates a PO, whether that is through their own EDI connection, in the portal, or both, the buyer still receives the EDI documents they are expecting in the format they require.

When a buyer updates their requirements, Procurant adjusts the outbound mapping and rules for that retailer. In most cases, the supplier does not need to change how they connect to stay compliant. The main exception is when the buyer’s new requirements depend on information that was not previously provided, which may mean the supplier needs to supply an additional detail going forward.

So, when you're on Procurant, you're covered regardless of a buyer's changing EDI specs or requirements!