Commerce Hub
1. Overview
The CommerceHub Integration in XoroERP enables automated exchange of EDI documents between retailers, CommerceHub, and XoroERP. This integration supports purchase order import, shipment confirmations, ASN processing, invoice transmission, and inventory synchronization while ensuring controlled and traceable data exchange.
CommerceHub acts as a centralized network that connects retailers and suppliers. Through this integration, XoroERP automatically receives purchase orders from CommerceHub and sends shipment confirmations, ASNs, invoices, and inventory updates back to the retailers via CommerceHub.
This integration is designed for operations and support teams to efficiently manage dropship and retail fulfillment transactions while minimizing manual intervention.
Key benefits include:
Automated order import from retail trading partners
Accurate shipment confirmation and ASN transmission
Reliable invoice processing for billing reconciliation
Inventory synchronization with retailer networks
Centralized monitoring through the Operations Page
2. Workflow
2.1 Order Import Flow (EDI 850)
Sequence: Retailer → CommerceHub → XoroERP
Purchase orders are generated by retailers and transmitted through CommerceHub to XoroERP.
During the import process:
CommerceHub sends EDI 850 Purchase Orders to XoroERP.
Orders are created in the configured store and warehouse location within XoroERP.
Based on configuration settings, orders may be auto-released for fulfillment after import.
Item matching is performed using identifiers such as UPC, GTIN, SKU, or retailer item numbers.
If multiple warehouse locations are configured, orders may be split by location.
Any validation or mapping errors encountered during import are logged for review.
2.2 Shipment Confirmation Flow (EDI 856)
Sequence: XoroERP → CommerceHub → Retailer
Once orders are fulfilled in XoroERP:
Shipment confirmations are generated.
EDI 856 Advance Shipping Notice (ASN) documents are created.
Shipment details including tracking number, carrier, shipped quantities, and ship date are sent to CommerceHub.
CommerceHub forwards the shipment confirmation to the retailer.
This ensures retailers receive shipment updates in real time.
2.3 Invoice Transmission Flow (EDI 810)
Sequence: XoroERP → CommerceHub → Retailer
After shipment confirmation:
XoroERP generates EDI 810 Invoice documents.
The invoice includes order references, item details, quantities, and pricing information.
The invoice is transmitted to CommerceHub and then delivered to the retailer for billing and reconciliation.
2.4 Inventory Synchronization
Inventory synchronization ensures retailers have accurate stock availability information.
When enabled:
Inventory levels are exported from XoroERP to CommerceHub.
Inventory updates typically run on a scheduled basis (daily or as configured).
Inventory can be filtered by store, warehouse location, or item tags.
This helps retailers maintain accurate stock visibility and prevents overselling.
2.5 Error Handling & Reprocessing
If an import or export process encounters errors:
The system logs the error with detailed messages.
Failed records can be reviewed from the Operations Page.
After correcting configuration or data issues, users can retry processing without affecting successfully processed records.
This ensures reliable EDI operations and quick issue resolution.
3. Settings
These settings define how purchase orders, shipment confirmations, invoices, and inventory synchronization are processed through the CommerceHub integration.
3.1 Data Export Settings
These settings define the accounts and configurations used when exporting shipment confirmations, invoices, and inventory updates to CommerceHub.
This configuration can be modified later as needed.
3.2 Auto Wave Sales Orders
This configuration controls whether imported orders should be automatically released and waved for fulfillment within XoroERP.
When enabled, orders received from CommerceHub can automatically move into the fulfillment workflow.
3.3 EDI Document Controls
These settings control which EDI documents are sent or received through the integration.
Examples include:
Purchase Orders (EDI 850)
Shipment Confirmations (EDI 856)
Invoices (EDI 810)
Functional Acknowledgements (EDI 997)
These controls allow administrators to manage document exchange behavior.
3.4 General Settings
General settings define integration behavior such as:
Default store and warehouse location
Trading partner configuration
Item identifier mapping rules
Processing automation preferences
These settings ensure that imported orders are mapped correctly within XoroERP.
3.5 Inventory Sync Settings
Inventory synchronization settings determine how and when inventory data is exported to CommerceHub.
Administrators can configure:
Inventory sync schedule
Store and warehouse filters
Item tag filters
This ensures that only relevant inventory is shared with retail partners.
4. Operations Page
The Operations Page serves as the central interface for monitoring and managing CommerceHub EDI activity.
Users can review document status, retry failed records, and monitor the overall health of the integration.
Header Options
Import Data Manually triggers the import of EDI documents from CommerceHub into XoroERP.
Start Date Defines the beginning of the date range for importing EDI documents.
End Date Defines the end of the date range for importing EDI documents.
Import Executes the import process based on the selected date range and configured document types.
Previous Exports
This section displays a history of outbound EDI documents sent from XoroERP to CommerceHub.
Users can:
Track document status
Review processing messages
Retry failed records if needed
5. Operations Tabs
5.1 Orders
The Orders tab manages inbound and outbound order transactions processed through CommerceHub.
Purpose
To track, process, and resolve issues related to order synchronization between CommerceHub and XoroERP.
Fields / Displayed Data
Order # – Unique order identifier in XoroERP.
Trading Partner – Retail partner associated with the order.
Document Type – Type of EDI document (e.g., Purchase Order 850).
Last Execution Date – Timestamp of the most recent processing attempt.
Message – Displays validation messages, errors, or processing status.
Options
Run – Reprocesses selected order records.
Mark as Resolved – Marks the order as successfully processed.
Mark as Unresolved – Reopens the order for reprocessing.
Filters
Hide Resolved Records – Hides orders already marked as resolved.
Show Errors Only – Displays only orders with processing errors.
5.2 Purchase Orders
The Purchase Orders tab tracks inbound purchase order documents received from CommerceHub.
Purpose
To monitor and manage purchase orders imported from retailers through CommerceHub.
Fields
Purchase Order # – Retailer's purchase order reference.
Trading Partner – Retail partner sending the order.
Last Execution Date – Timestamp of the last processing attempt.
Message – Displays processing details or validation errors.
Options
Run – Reprocess selected purchase orders.
Mark as Resolved – Marks successfully processed records.
Mark as Unresolved – Reopens the purchase order for reprocessing.
5.3 ASNs
The ASNs tab tracks outbound Advance Shipping Notices (EDI 856) sent from XoroERP to CommerceHub.
Purpose
To ensure shipment information is successfully transmitted to retailers.
Fields
ASN # – Unique ASN identifier.
Order Reference – Associated order number.
Last Execution Date – Timestamp of the last export attempt.
Message – Displays export status or errors.
5.4 Invoices
The Invoices tab tracks outbound EDI 810 Invoice documents sent from XoroERP through CommerceHub.
Purpose
To ensure invoice information is successfully transmitted for billing reconciliation.
Fields
Invoice # – Unique invoice reference.
Trading Partner – Invoice recipient.
Last Execution Date – Timestamp of the export attempt.
Message – Displays transmission status or errors.
5.5 Logs
The Logs tab records all CommerceHub EDI activities, providing a full audit trail of integration operations.
Purpose
To monitor, troubleshoot, and verify all EDI interactions between XoroERP and CommerceHub.
Columns / Information Displayed
Execution Date – Date and time of the EDI operation.
Document Type – Order, Purchase Order, ASN, or Invoice.
Trading Partner – Source or destination of the document.
Reference # – Associated order, ASN, or invoice reference.
Message – Detailed processing information or error messages.
Filters & Options
Do Not Show Resolved Records – Hides records marked as resolved.
Filter by Document Type – Filters logs by Orders, ASNs, or Invoices.
Last updated
Was this helpful?