Event Log
The Event Log is the complete audit trail for every order and purchase order in your OMS. It records every system action, status change, and communication with external systems.
Use this log to track progress, diagnose issues, understand automation, and resolve discrepancies.
- OMS Status is the high-level summary of the order's current state (e.g.,
Warehouse Processing). - Event Type/Sub-Type are the specific, detailed actions that occur, often many within a single status phase.
For example, an order with an OMS Status of
Warehouse Processingcan have events for being sent to the warehouse, received by the warehouse, and fulfilled by the warehouse, all before the status finally changes toShipped.
Event Categories & Types
Order Creation & Import
These events track how an order enters the OMS.
| Event Type | Description |
|---|---|
| API Import | Order was created via an automated API connection (e.g., from Shopify, Amazon through Item DI). |
| EDI Import | Order was created via an EDI document (e.g., an EDI 850 Purchase Order from a retail partner). |
| Manual Import | Order was created by uploading a file or importing data manually. |
| Reimport After Cancel | A previously canceled order was re-imported and reactivated. |
| Create Failed | The initial attempt to create the order failed due to data validation errors. |
Fulfillment Routing & Allocation
These events show the order's journey to a fulfillment center.
| Event Type | Description |
|---|---|
| Auto Dispatch | The system automatically assigned the order to a warehouse based on routing rules. |
| Manual Dispatch | A team member manually assigned the order to a specific warehouse. |
| Dispatch Retry | The system is re-attempting to assign the order after a previous failure. |
| Manual Deallocate | A team member removed the warehouse assignment. The order will be sent back for re-routing. |
| Warehouse Cancel | The assigned warehouse canceled the order (e.g., due to a physical stock discrepancy). |
Order Content & Detail Changes
These events record modifications made to the order's contents or information.
| Event Type | Description |
|---|---|
| Product Add/Remove/Qty Change/Replace | The items or quantities in the order were modified. |
| Address Change | The shipping address was updated. |
| Contact Info Change | The customer's phone number or email was updated. |
| Customer Note Change | A note visible to the customer was added or edited. |
| Internal Note Added | An internal note for the operations team was added. |
| Tag Added/Removed | A label for filtering or categorization was applied or removed. |
Fulfillment & Delivery Confirmation
These events track the physical fulfillment and electronic confirmation processes.
| Event Type | Sub-Type | Description |
|---|---|---|
| Fulfilled | FulfilledByWMS | The warehouse reported the order has been physically packed and shipped. |
| DC/Document Processing | DCSentToSystem | Sales Orders: An EDI 856 Advance Ship Notice was sent to the partner. Purchase Orders: Shipping details were sent to the warehouse for inbound receiving. |
| DC/Document Processing | DCRetrieval | Acknowledgment was received from the partner/warehouse confirming document receipt. |
| Shipment Tracking | In Transit / Out For Delivery | Carrier tracking updates received. |
| Shipment Tracking | Delivered / Delivery Failed / Refused | Final delivery outcomes. |
Cancellations & Returns
These events track the cancellation process and post-purchase returns or exchanges.
| Event Type | Description |
|---|---|
| Cancel By Customer | The cancellation was initiated by the customer. |
| Manual Cancel | The cancellation was performed manually by a team member. |
| Timeout Cancel | The order was canceled automatically by a time-based rule. |
| Refund/Return/Exchange Initiated/Completed | Tracks the progress of post-purchase customer service workflows. |
Hold & Release Management
These events show when an order was paused ("held") and when it was released.
| Event Type | Description |
|---|---|
| System Hold | The order was placed on hold automatically by a business rule. |
| Manual Hold | A team member manually placed the order on hold. |
| Manual Release / System Auto Release | The hold was removed, allowing fulfillment to continue. |
Errors & Failures
These events indicate a problem has stopped the order's progress.
| Event Type | Description & Suggested Action |
|---|---|
| Push Failed To WMS (Create) | Failed to send a new order/PO to the WMS. Action: Check warehouse connectivity and order data. |
| Push Failed To WMS (DC Missing) | Failed to send fulfillment details. Missing data package. Action: Check for missing required fields (UOM, carrier codes, etc.). |
| Allocation Failed (SKU Unavailable) | No warehouse has sufficient stock. Action: Check inventory or create a purchase order. |
| Warehouse SKU Not Found | The SKU does not exist in the target WMS. Action: Ensure product is synced with the warehouse. |
| Field Invalid (Product Not Found) | The product SKU does not exist in the OMS. Action: Add the product to the OMS catalog. |
| Address Invalid / Validation Failed | The shipping address is incorrect or unverifiable. Action: Contact the customer. |
| System Error / External System Error | A generic technical failure. Action: Contact IT support if it persists. |
Troubleshooting Common Issues
Use the Event Log as your first step when diagnosing problems.
| If you see this issue... | Look for these Event Types... | What it typically means... |
|---|---|---|
| Order is stuck in "On Hold" or "Exception" | Allocation Failed, System Hold, Push Failed To WMS (Create) | The system can't find stock, a rule paused it, or it couldn't be sent to any warehouse. |
| Order is in "Warehouse Processing" but not shipping | FulfilledByWMS without subsequent DCSent or tracking events | The warehouse has shipped it, but the electronic confirmation to the partner is pending or failed. |
| Order is in "Exception" status | Any event in the Errors & Failures category. | A specific problem needs resolution. Check the event details for the exact error. |
| PO is not being received by the warehouse | Push Failed To WMS (DC Missing) | The purchase order is missing required receiving details (e.g., carrier info, expected date). |