11 exception types, 2-phase resolution workflow, per-item tracking, and automatic channel push-back. From the moment an issue is reported to the moment it's resolved — nothing falls through the cracks.
Post-order issues are inevitable. What matters is how you track and resolve them. Here's how OrderHUBx transforms exception management.
| Without OrderHUBx | With OrderHUBx |
|---|---|
| ✕ Exceptions tracked in spreadsheets or sticky notes | ✓ Dedicated exception system with status lifecycle |
| ✕ No visibility into what's pending vs resolved | ✓ PENDING → APPROVED → PROCESSING → COMPLETED pipeline |
| ✕ Returns, refunds, claims tracked separately | ✓ Single exception record links returns, refunds, claims, and replacements |
| ✕ Partial returns require manual tracking | ✓ Per-item resolution — return 2 of 10 items, replace 1, refund 1 |
| ✕ Channel status out of sync after cancellation | ✓ Automatic push-back to Walmart, WooCommerce, Amazon FBM |
| ✕ Financial impact scattered across systems | ✓ Refund, claim, and charge tracking with independent status flags |
| ✕ No audit trail for disputes | ✓ Complete order history log (every action timestamped) |
Every post-order issue has a defined workflow with the right resolution actions.
Cancel full order or line items pre/post-shipment. Includes stock reversal and channel push-back.
Product arrived damaged. Return + replacement + shipper claim.
Incorrect item shipped. Return + correct replacement.
Item from order is missing. Replacement + shipper claim.
Product not functioning. Return + replacement.
Item doesn't match listing. Return + refund.
Customer needs delivery address updated before shipment.
Customer requests faster delivery. Includes charge agreement tracking.
Customer picks up instead of ship. Generates PICKUP label with $0 shipping.
Shipping delayed due to weather. Informational tracking.
Miscellaneous issues with flexible resolution options.
Exception dashboard — see every open issue, its status, and resolution progress at a glance.
Each exception type has a defined set of resolution actions. The system shows only the relevant options — no guesswork.
| Exception Type | Return? | Replacement? | Refund? | Shipper Claim? | Channel Push-back? |
|---|---|---|---|---|---|
| Cancellation | If shipped | No | Yes | No | Yes (WC/Walmart/FBM) |
| Damaged | Yes | Yes | Optional | Yes | No |
| Wrong Item | Yes | Yes (correct SKU) | Optional | No | No |
| Missing | No | Yes | Optional | Yes | No |
| Defective | Yes | Yes (same SKU) | Optional | No | No |
| Not As Described | Yes | Optional | Yes | No | No |
| Address Change | No | No | No | No | No |
| Expedite Delivery | No | No | No | No | No |
| Office Pickup | No | No | No | No | No |
| Weather Delay | No | No | No | Optional | No |
| Other | Optional | Optional | Optional | Optional | No |
Phase 1 captures the issue. Phase 2 resolves it. Clear separation ensures nothing gets lost.
One exception can have item A returned + refunded, item B replaced with a different SKU, and item C written off — each tracked independently.
| Per-Item Field | Values | Purpose |
|---|---|---|
| Resolution Status | PENDING → APPROVED → PROCESSING → COMPLETED | Track where each item stands |
| Return Required | Yes / No | Does the customer need to send it back? |
| Return Timing | NOW or AFTER_RETURN | Send replacement before or after return received |
| Restockable | Yes / No | Can be restocked or write-off |
| Exchange Flag | Yes / No | Replacement being sent |
| Exchange New SKU | SKU reference or same product | Alternative SKU or same product |
| Refund Amount | $ per item | Amount to refund for this specific item |
Per-item resolution — each item gets its own return, replacement, and refund decision.
Refunds, shipper claims, and customer charges — each with independent status tracking.
| Flag | Tracks | Lifecycle |
|---|---|---|
| Refund Status | Customer refund payment | PENDING → PAID |
| Claim Status | Shipper insurance claim | PENDING → RECEIVED |
| Charge Status | Customer charge (restocking/expedite fee) | PENDING → PAID |
| Return Status | Physical return lifecycle | REQUESTED → RECEIVED → INSPECTED |
Every exception follows a clear status pipeline from creation to completion.
Just logged, awaiting review.
Reviewed and approved for processing.
Resolution actions underway (returns/refunds pending).
All resolution actions settled.
Invalid or declined exception.
Pending customer or third-party response.
When you cancel an order in OrderHUBx, the cancellation is pushed back to the sales channel automatically.
Cancel in OrderHUBx → status syncs to Walmart automatically.
Cancel in OrderHUBx → WooCommerce order updated via API.
Cancel in OrderHUBx → Amazon FBM order cancelled.
A complete walkthrough of how a damaged item exception flows from report to resolution.
Complete damaged item workflow — from initial report through automated resolution processing.
Beyond standard returns and refunds, the exception system handles these specialized workflows.
Generates PICKUP-YYYYMMDD-NNNN reference with 4x6 label. $0 shipping rate. Green PICKUP badge on order list. Excluded from carrier tracking.
Required delivery date field + customer charge agreement. Flags order as expedited. Can charge customer for upgrade.
Customer keeps the item. No physical return, no stock increase. Used for low-value items or goodwill gestures.
Return 2 of 10 items from a line. Original line reduced, each returned item tracked independently with its own resolution status.
Exception handling is a core module included with every OrderHUBx plan.
See how OrderHUBx exception handling keeps every issue visible, every resolution documented, and every dollar tracked.