CEVA Logistics has acquired the Shipwire business to become the world's 5th largest logistics provider.

We're Here to Help

EDI Preparation: Setup Your Product Catalog in the Shipwire Platform


How to setup your product catalog in the Shipwire Platform

In preparation for utilizing our Commerce EDI solution, the product catalog in your Shipwire platform account must be established for EDI purposes. The ideal product catalog set-up is as follows:

Step 1: Ensure that all of the SKUs you intend on selling have been added to the Shipwire product catalog. See HERE for tips.

If this is not completed, then orders for SKUs not in the Shipwire Platform will fail to import, and products will need to be added to the product catalog in a reactive fashion.

Step 2: Export your Shipwire product catalog and share with retailer(s) for them to add the Shipwire SKUs as vendor numbers. You may need to supplement this data with UPC and other info the retailer may require.

If this is done, then a matching file is typically not required (ie not for retail replenishment orders, but sometimes for dropship inventory sync), and orders will not fail in Logicbroker or fail to import into the Shipwire Platform.


However, if the above process is not followed, and different SKUs are given to the retailer(s), then a matching file will need to be created to translate the SKUs provided to the retailer to the SKUs as they are in the Shipwire Platform product catalog. This will then be used for translating SKUs on all incoming POs for this retailer. Any time a PO is received which contains a SKU not given in the matching file, the order will fail to import and the product will need to be added to the matching file in a reactive fashion. To set this up, please work with your Ingram Micro Customer Success point of contact and Logicbroker.

An alternate path to providing a matching file for B2B retail replenishment may be entering aliases (alternate names) for the SKUs or UPCs provided to the retailer so that the POs can be imported properly. This typically works unless the retailer has unusual EDI requirements. The downside to this, of course, is that you must remember to add the appropriate aliases for every new product you add to the Shipwire Platform. If you forget, orders containing this SKU will fail. The ideal here is using the UPC as an alias, if you’re not using UPC as the SKU in the Shipwire Platform.

{% block invis %}{% endblock %}