> ## Documentation Index
> Fetch the complete documentation index at: https://help.jetpack3pl.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Avoid These Common WRO Mistakes

> Prevent receiving delays and inventory issues by avoiding these seven common WRO mistakes that cause processing problems and extra fees.

<div className="page-intro">
  Even experienced merchants sometimes make mistakes when creating Warehouse Receiving Orders. Understanding these common errors helps you avoid receiving delays, unexpected fees, and inventory accuracy issues.
</div>

## The Seven Most Common WRO Mistakes

Learning from these frequent mistakes saves time, reduces fees, and keeps your inventory flowing smoothly through receiving.

***

### 1. Incorrect Inventory Quantity in WRO

**The Mistake**: The quantity entered in your WRO doesn't match the actual quantity shipped.

| What Goes Wrong                                | Why It Matters                                                                                                                                                                                                                     |
| ---------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **WRO shows 100 units, shipment contains 150** | <ul><li>Creates [Unidentified Receiving Order (URO)](/fulfillment/sending-inventory/unidentified-receiving-orders) for 50 extra units</li><li>URO processing fees apply</li><li>Delays availability of overage inventory</li></ul> |
| **WRO shows 100 units, shipment contains 75**  | <ul><li>WRO remains "Partially Arrived" indefinitely</li><li>Expected inventory never becomes available</li><li>Requires manual WRO adjustment</li></ul>                                                                           |

**How to Prevent**:

* Count inventory carefully before creating WRO
* Update WRO if quantities change after creation (see [Editing WROs](/fulfillment/sending-inventory/editing-wro))
* Double-check quantities before shipping
* Use packing lists to verify counts during shipping prep

***

### 2. Mixing SKUs in Single Shipping Units

**The Mistake**: Packing multiple different SKUs in the same box or pallet.

**Example Scenario**: You pack blue shirts, red shirts, and green shirts all in the same box because they're similar products.

| What Goes Wrong              | Impact                                                                                                                                              |
| ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Receiving delays**         | <ul><li>Warehouse teams must separate and count each SKU individually</li><li>Takes significantly longer than processing single-SKU boxes</li></ul> |
| **Accuracy risks**           | <ul><li>Higher chance of counting errors</li><li>More complex verification process</li></ul>                                                        |
| **Additional fees possible** | <ul><li>May incur extra handling charges for complex receiving</li><li>Especially if separation requires significant labor</li></ul>                |

**How to Prevent**:

* Pack only one SKU per box or pallet
* If variants exist (colors, sizes), keep each variant in separate boxes
* Label boxes clearly with SKU information
* Create separate WRO line items for each SKU, even if quantities are small

<Info title="Exception: Product Bundles">
  Pre-configured [product bundles](/fulfillment/managing-products/more-tools/creating-product-bundles) are the exception—these can include multiple SKUs because they're set up as a single unit in your Product Catalog.
</Info>

***

### 3. Long Gaps Between Shipment Arrivals

**The Mistake**: Units for a single WRO arrive more than 28 days apart.

**Example Scenario**: You ship 5 boxes on November 1st and they arrive November 5th. You ship 5 more boxes on December 10th for the same WRO.

| What Happens                | Consequences                                                                                                                                        |
| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| **WRO marked complete**     | <ul><li>After 28 days with no new arrivals, WRO is automatically marked complete</li><li>Late-arriving boxes trigger a new URO</li></ul>            |
| **URO processing required** | <ul><li>Late boxes processed as unidentified inventory</li><li>URO fees apply</li><li>Extra processing time delays inventory availability</li></ul> |

**How to Prevent**:

* Ship all boxes for a WRO within five days of the first arrival
* For split shipments, create separate WROs if timing will be spread out
* Enter tracking numbers promptly so Jetpack can monitor arrival patterns
* Consolidate shipments when possible

***

### 4. Failing to Mark DG/HAZMAT Products

**The Mistake**: Not configuring dangerous goods or hazardous materials with Safety Data Sheets (SDS) before shipment arrives.

**Dangerous Goods Include**:

* Products with lithium batteries
* Aerosols and pressurized containers
* Flammable liquids (perfumes, alcohol-based products)
* Corrosive materials
* Products requiring HAZMAT shipping labels

| What Goes Wrong        | Serious Consequences                                                                                                                                               |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Legal violations**   | <ul><li>Warehouse receives improperly documented HAZMAT</li><li>Regulatory fines from government agencies</li><li>Fines charged directly to your account</li></ul> |
| **Shipment rejection** | <ul><li>Inventory may be refused at receiving</li><li>Return shipping costs charged to you</li></ul>                                                               |
| **Liability issues**   | <ul><li>Safety risks for warehouse personnel</li><li>Potential facility violations</li></ul>                                                                       |

**How to Prevent**:

* Review product ingredients and materials for HAZMAT classifications
* Configure products with SDS **before creating WRO**
* Include HAZMAT markings on shipping labels when required
* Learn more: [Dangerous Goods + Hazmat](/fulfillment/goods-policies/dangerous-goods-hazmat)

<Warning title="Client Responsibility">
  You are fully responsible for identifying and properly marking dangerous goods. All fines and penalties resulting from unmarked HAZMAT will be charged to your account.
</Warning>

***

### 5. Missing Tracking Numbers

**The Mistake**: Failing to enter tracking numbers for your WRO shipment.

**Why Tracking Matters**:

* **Capacity planning**: Jetpack uses tracking to anticipate arrivals and allocate receiving capacity
* **Prioritization**: Urgent shipments can be prioritized if arrival time is known
* **Issue resolution**: Quickly identify and resolve shipment delays or lost packages

| Impact of Missing Tracking    | Results                                                                                                                      |
| ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| **Slower processing**         | <ul><li>Shipments without tracking processed on first-come basis</li><li>No priority for time-sensitive inventory</li></ul>  |
| **Difficult troubleshooting** | <ul><li>Can't verify if shipment was delivered to correct location</li><li>Hard to resolve receiving discrepancies</li></ul> |
| **Limited visibility**        | <ul><li>You can't monitor shipment progress</li><li>No proactive notification of delays</li></ul>                            |

**How to Prevent**:

* Enter tracking numbers **immediately after shipping**
* Use individual tracking numbers for each box (not master tracking)
* Verify tracking format matches carrier requirements (see [Sending Parcels](/fulfillment/sending-inventory/best-practices/sending-parcels))
* Update WRO if additional tracking numbers become available

***

### 6. Omitting Lot Numbers for Lot Products

**The Mistake**: Forgetting to add lot numbers and expiration dates when creating a WRO for lot-tracked products.

**Critical Problem**: Once receiving begins, you cannot edit lot information. This creates major issues:

| What Goes Wrong           | Severe Impact                                                                                                                                                         |
| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Cannot fulfill orders** | <ul><li>Products without lot numbers can't be picked for shipment</li><li>Inventory becomes unavailable even though physically present</li></ul>                      |
| **Expensive fixes**       | <ul><li>Adding lot info to received inventory after processing requires manual intervention</li><li>Requires physical inventory location and manual updates</li></ul> |
| **Compliance violations** | <ul><li>Products requiring lot tracking for regulatory reasons become non-compliant</li><li>Cannot perform recalls if lot numbers aren't recorded</li></ul>           |

**How to Prevent**:

* Verify products are configured as [lot products](/fulfillment/sending-inventory/best-practices/lot-products) before creating WRO
* Gather lot numbers and expiration dates from manufacturer before shipping
* Double-check lot information is entered in WRO before submitting
* Never mix different lot numbers in the same box or pallet

<Warning title="Cannot Edit After Processing Starts">
  Lot numbers cannot be added or edited once receiving begins. Always verify lot information is complete before submitting your WRO.
</Warning>

***

### 7. Sending Inactive SKUs

**The Mistake**: Shipping products that are marked as "Inactive" in your Product Catalog.

**Why This Happens**:

* Product was deactivated in your store but inventory was already en route
* Old SKUs reactivated without updating product status in dashboard
* Discontinued products sent by mistake

| What Happens              | Consequences                                                                                                                                              |
| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Won't be received**     | <ul><li>Inactive SKUs are not processed during receiving</li><li>Units sit in receiving area unprocessed</li></ul>                                        |
| **Triggers URO**          | <ul><li>Shipment moved to URO for manual intervention</li><li>URO processing fees apply</li><li>Significant delay before inventory is available</li></ul> |
| **Requires reactivation** | <ul><li>Must reactivate product in dashboard</li><li>Contact Jetpack Care to process URO</li><li>Additional time and fees involved</li></ul>              |

**How to Prevent**:

* Verify all products in WRO are marked "Active" in [Product Catalog](/fulfillment/managing-products)
* Review product status before creating WRO
* Reactivate discontinued products if sending inventory for liquidation or returns
* Maintain accurate product catalog with current active/inactive status

***

## Best Practices Checklist

Before submitting any WRO, verify:

* [ ] **Quantities are accurate** and match what you're actually shipping
* [ ] **Each box contains only one SKU** (or one variant)
* [ ] **All boxes will arrive within 28 days** of first shipment
* [ ] **HAZMAT products are configured** with SDS before shipping
* [ ] **Tracking numbers are entered** for all shipments
* [ ] **Lot numbers and expiration dates are complete** for lot products
* [ ] **All products are active** in your Product Catalog

Following this checklist prevents the vast majority of WRO issues and ensures smooth, fast receiving.

***

## Let's Dive Deeper

<CardGroup cols={3}>
  <Card title="Sending Inventory Overview" icon="warehouse" href="/fulfillment/sending-inventory">
    Back to the main guide on our receiving process
  </Card>

  <Card title="Creating a WRO" icon="file-plus" href="/fulfillment/sending-inventory/creating-wro">
    Learn how to create error-free Warehouse Receiving Orders
  </Card>

  <Card title="Editing a WRO" icon="pen-to-square" href="/fulfillment/sending-inventory/editing-wro">
    Fix mistakes in your WRO before shipping
  </Card>

  <Card title="Unidentified Shipments (UROs)" icon="triangle-exclamation" href="/fulfillment/sending-inventory/unidentified-receiving-orders">
    Learn what happens when WRO mistakes occur
  </Card>

  <Card title="Creating + Managing Lot Products" icon="layer-group" href="/fulfillment/sending-inventory/best-practices/lot-products">
    Understand lot tracking requirements and setup
  </Card>

  <Card title="Dangerous Goods + Hazmat" icon="radiation" href="/fulfillment/terms-and-slas/dangerous-goods-hazmat">
    Configure HAZMAT products correctly before shipping
  </Card>
</CardGroup>

<div className="jetpack-callout">
  <img src="https://mintcdn.com/jetpack/2iejPNBTYKEx6ntF/images/jetpack-logomark-256.png?fit=max&auto=format&n=2iejPNBTYKEx6ntF&q=85&s=340604ced4add3864f2641341826e1c9" alt="Jetpack" className="jetpack-callout-icon" width="256" height="256" data-path="images/jetpack-logomark-256.png" />

  <div className="jetpack-callout-content">
    <h4 className="jetpack-callout-title">Questions? Contact Jetpack Care.</h4>
    <p className="jetpack-callout-text">If you have any questions or run into issues, you can always contact Jetpack Care for help. Our team is always here to assist via Slack, phone, or email!</p>
  </div>
</div>