> ## 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.

# Unidentified Receiving Orders (URO)

> Policy and procedures for resolving unidentified receiving orders at Jetpack fulfillment centers

<div className="page-intro">
  Unidentified Receiving Orders (UROs) are assigned when incoming shipments cannot be received within standard turnaround times due to missing or inaccurate information. Understanding URO triggers and resolution procedures helps you avoid delays and additional fees.
</div>

## What is a URO?

When a shipment arrives at a Jetpack fulfillment center without proper identification or documentation, the system places the boxes or pallets on hold and assigns a URO Tag number for tracking purposes.

<Info>
  **Basic Requirement:** Every box or pallet that arrives at a Jetpack fulfillment center must have a Warehouse Receiving Order (WRO) or associated tracking number.
</Info>

Without this information, receiving teams cannot process your inventory, resulting in a URO assignment.

## Key Policy Terms

<Warning>
  **Automatic Disposal:** Jetpack will dispose of any un-linked URO automatically after 90 days. This timeline is firm to manage warehouse capacity and maintain operational efficiency.
</Warning>

### WRO Completion Timeline

<Info>
  All WROs are marked complete 28 days after the first box or pallet delivery, regardless of whether all expected boxes have arrived at the fulfillment center.
</Info>

**Important Implications:**

* Shipments arriving after the 28-day window will trigger UROs
* Split shipments must arrive within 28 days to avoid UROs
* Delayed freight may result in URO fees

## URO Pricing (USA Hubs)

Each URO type has a grace period before daily storage fees begin to accrue.

| URO Type            | Grace Period | Daily Cost |
| ------------------- | ------------ | ---------- |
| No WRO              | 24 Hours     | \$25       |
| WRO Overage         | 72 Hours     | \$10       |
| Lot Number Mismatch | 72 Hours     | \$10       |
| Barcode Issue       | 72 Hours     | \$10       |
| Return to Sender    | 96 Hours     | \$5        |
| Other Issues        | 72 Hours     | \$10       |

<Warning>
  Fees begin accruing immediately after the grace period ends and continue daily until the URO is resolved or reaches the 90-day disposal threshold.
</Warning>

## Common URO Triggers

Understanding what causes UROs helps you prevent them from occurring.

<AccordionGroup>
  <Accordion title="Missing Documentation">
    **No WRO Created:**

    * Shipment sent without creating a warehouse receiving order
    * WRO created after inventory already shipped
    * WRO not submitted or saved properly

    **Missing Tracking Information:**

    * No tracking number provided on WRO
    * Incorrect tracking number entered
    * Tracking number not linked to shipment
  </Accordion>

  <Accordion title="Quantity Discrepancies">
    **WRO Overage:**

    * Additional unlisted items included in shipment
    * Quantity discrepancies exceeding 10% variance
    * Quantity discrepancies exceeding 25+ units
    * Extra boxes not documented on WRO

    **Resolution Required:**

    * Update WRO to reflect actual quantities
    * Create additional WRO for overage items
  </Accordion>

  <Accordion title="Product Configuration Issues">
    **Barcode Problems:**

    * Incorrect barcodes on products
    * Missing barcodes on units
    * Barcodes not matching product catalog
    * Damaged or unreadable barcodes

    **Unlabeled Similar SKUs:**

    * Multiple similar products without clear identification
    * Products lacking distinguishing barcodes
    * Variants not properly labeled
  </Accordion>

  <Accordion title="Special Product Issues">
    **Lot Number Mismatches:**

    * Lot numbers on products don't match WRO
    * Missing lot number information
    * Incorrect lot number formatting

    **Digital/Merged Items:**

    * Digital products incorrectly sent to fulfillment center
    * Merged SKUs not properly configured
    * Virtual products shipped as physical inventory

    **Dangerous Goods:**

    * HAZMAT products without proper approval
    * Missing Safety Data Sheets
    * Incorrect dangerous goods classification
  </Accordion>

  <Accordion title="Timing and Documentation Errors">
    **Late Arrivals:**

    * Shipments arriving after 28-day WRO window closed
    * Delayed freight not communicated
    * Split shipments with extended delivery timelines

    **Return Order Issues:**

    * Improperly marked return orders
    * Returns without proper authorization
    * Customer returns sent as new inventory

    **Duplicate Labels:**

    * Same box label used on multiple boxes
    * Copied or reprinted box labels
    * Non-unique identification numbers
  </Accordion>
</AccordionGroup>

## Resolution Process

Follow these steps to resolve a URO and avoid ongoing daily fees.

<Steps>
  <Step title="Review Notification Email">
    Jetpack sends an automated email when a URO is created, including:

    * URO ID number
    * Fulfillment center location
    * Brief description of the issue
    * Images of received items (when available)
  </Step>

  <Step title="Access On Hold Receiving">
    Navigate to the **On Hold Receiving** section in your Jetpack dashboard to view all pending UROs.
  </Step>

  <Step title="Verify Item Ownership">
    Review provided images and descriptions to confirm the items belong to your account. Contact Jetpack Care immediately if items are not yours.
  </Step>

  <Step title="Create or Link WRO">
    **Option 1: Create New WRO**

    * Create a new warehouse receiving order
    * Include the URO ID number in the WRO details
    * Specify all items and quantities

    **Option 2: Link Existing WRO**

    * Locate the appropriate WRO in "Awaiting Arrival" status
    * Add the URO ID to the WRO
    * Update quantities if needed
  </Step>

  <Step title="Include Box Numbers">
    Add the associated box number or pallet ID from the URO notification to ensure proper matching.
  </Step>

  <Step title="Save and Submit">
    Save your completed WRO to trigger the receiving process. The URO will be resolved within 24-48 hours.
  </Step>
</Steps>

<Info>
  **WRO Status Requirement:** Only WROs in "Awaiting Arrival" status can be linked to UROs. WROs marked as "Complete" cannot be reopened or linked.
</Info>

## Prevention Best Practices

Avoid UROs by following these best practices:

<Tabs>
  <Tab title="Before Shipping">
    **Create WRO First:**

    * Always create your WRO before shipping inventory
    * Double-check all product SKUs and quantities
    * Include accurate tracking information
    * Save and submit WRO before generating box labels

    **Verify Product Setup:**

    * Ensure all SKUs exist in product catalog
    * Confirm barcodes are correctly configured
    * Check for special requirements (lot tracking, expiration dates)
    * Verify HAZMAT products have approval
  </Tab>

  <Tab title="During Preparation">
    **Proper Labeling:**

    * Apply unique box labels to each carton
    * Ensure barcodes are clean and scannable
    * Include WRO number on box labels
    * Don't reuse or duplicate labels

    **Accurate Packaging:**

    * Ship only items listed on WRO
    * Don't include extra products or samples
    * Separate different WROs into different shipments
    * Use proper packaging for product types
  </Tab>

  <Tab title="Tracking & Communication">
    **Monitor Shipments:**

    * Add tracking numbers to WRO immediately
    * Monitor carrier tracking for delivery confirmation
    * Communicate delays to Jetpack Care
    * Ensure delivery within 28-day window

    **Special Circumstances:**

    * Contact Jetpack Care for split shipments
    * Notify team of freight delays
    * Update WRO if quantities change
    * Request extensions when needed
  </Tab>
</Tabs>

## URO Fee Management

<AccordionGroup>
  <Accordion title="Grace Periods">
    Each URO type includes a grace period before fees begin:

    * Use grace period to quickly resolve issues
    * Fees calculated from end of grace period
    * No retroactive fee waivers after grace period expires
  </Accordion>

  <Accordion title="Fee Calculation">
    Daily fees accrue based on URO type:

    * Fees charged per calendar day
    * Multiple UROs charged separately
    * Fees continue until resolution or disposal
    * Final fees added to monthly invoice
  </Accordion>

  <Accordion title="Fee Disputes">
    Contact Jetpack Care within 7 days if:

    * You believe the URO was created in error
    * System issues prevented proper WRO creation
    * Jetpack error caused the URO
    * You have documentation supporting your case
  </Accordion>
</AccordionGroup>

## 90-Day Disposal Policy

<Warning>
  **Automatic Disposal Timeline:**

  * Day 1-90: URO remains on hold, daily fees accrue
  * Day 90: Final notification sent to merchant
  * Day 91+: Inventory automatically disposed of
  * No refunds or compensation after disposal
</Warning>

**Disposal Process:**

* Inventory is removed from warehouse
* URO closed in system
* No recovery option available
* All accrued fees remain due

<Tip title="Questions About UROs?">
  If you receive a URO notification and are unsure how to resolve it, contact Jetpack Care immediately. Our team can help you identify the issue and walk you through the resolution process to minimize fees and prevent disposal.
</Tip>

## Related Resources

<CardGroup cols={2}>
  <Card title="Sending Inventory" icon="truck-ramp-box" href="/fulfillment/sending-inventory">
    Learn how to create proper warehouse receiving orders
  </Card>

  <Card title="Managing Products" icon="box" href="/fulfillment/managing-products">
    Configure products with correct barcodes and settings
  </Card>

  <Card title="Dangerous Goods + HAZMAT" icon="radiation" href="/fulfillment/terms-and-slas/dangerous-goods-hazmat">
    Ensure HAZMAT products have proper approval
  </Card>

  <Card title="Operations Errors Policy" icon="shield-check" href="/fulfillment/terms-and-slas/operation-errors-policy">
    Understand how receiving errors are handled
  </Card>
</CardGroup>