Module 01 — Warehouse to Order to Prep Workflow

Transcript / lesson notes

Module 01 — Warehouse to Order to Prep Workflow

This is the highest-priority workflow for Franz because a small misunderstanding here can create real operational confusion. Learn these five tiles first: Warehouse Inventory, SKU Mapping Validation, Restock Dashboard, Restock Order Form, and Prep & Pack Workspace.

1. Warehouse Inventory

Purpose: tracks physical stock, sections, counts, and events in the warehouse.

Current status: active build path. The inspected warehouse data showed 60 active products and 1,559 total units across shelf, golden, replacements, returns, and related counts. The future spec points toward movement tracking for received, pulled, adjusted, shipped, returned, and notes.

Main sources: warehouse inventory JSON, warehouse mapping overrides, section definitions, reconciliation notes, and eventually movement records.

Relationship: Warehouse Inventory protects Restock Dashboard and Order Form from buying product already in the building.

Escalate when physical stock and dashboard stock disagree, a product appears in the wrong section, or an old starting balance may be mistaken for current balance.

Ask Fergus: “Is this a starting balance, movement-adjusted balance, or manual note?”

Key section language:

• EXPIRING: stock Brent should watch first.
• ON SHELF: main warehouse shelf stock.
• GOLDEN: special stock. Do not assume it should be used automatically.

2. SKU Mapping Validation

Purpose: links Amazon SKUs, FNSKUs, and ASINs to doTERRA product IDs.

Current status: critical bridge tile. Inspected data showed 247 FNSKUs, 245 matched, 2 unmatched, 50 multipacks, and 288 reference products.

Main sources: SKU mapping JSON, reference products, kit contents, warehouse mapping overrides, and candidate matching logic.

Relationship: mapping errors propagate into Restock, Warehouse, Order Form, Prep, profitability, and sales analysis.

Escalate when one ASIN maps to multiple products, a multipack looks like a single, or a warehouse product has no clean product ID.

Ask Fergus: “Is this a duplicate-ASIN inherit case, a multipack, a kit, or a missing doTERRA Product ID?”

3. Restock Dashboard

Purpose: answers what should we order, how much, and why.

Current status: active and central. The inspected restock snapshot showed 298 SKUs, 75 needing restock, 3,240 total suggested units, and about $89,538.75 estimated order cost.

Main sources: FBA inventory, velocity, mapping, previous order reserve evidence, shipment details, and restock dashboard JSON.

Relationship: upstream of the Restock Order Form; depends heavily on SKU Mapping and Warehouse Inventory.

Escalate when a quantity seems too high or too low, a previous order may already cover demand, or a warehouse quantity should have reduced the order.

Ask Fergus: “Is this using the newest restock snapshot, and was previous-order reserve applied?”

Common failure modes:

• stale restock snapshot;
• previous-order reserve counted wrong;
• warehouse stock not applied;
• SKU mapping issue;
• duplicate ASIN or multipack issue;
• velocity spike causing an aggressive order recommendation.

4. Restock Order Form

Purpose: turns restock recommendations into an order draft.

Current status: active artifact. The inspected order-form artifact showed 46 products, 2,065 units, about $59,460 cost, and 54,935 PV.

Main sources: Restock Dashboard, doTERRA Product IDs, SKU Mapping, warehouse overlay quantities, and order history.

Relationship: downstream of Restock Dashboard and upstream of Prep & Pack Workspace.

Escalate when order quantities differ from restock recommendations, warehouse stock is unexpectedly included or excluded, or GOLDEN inventory appears to be used incorrectly.

Ask Fergus: “Is EXPIRING and ON SHELF stock automatically applied here, and is GOLDEN opt-in or excluded for this row?”

5. Prep & Pack Workspace

Purpose: turns an order into prep lanes, shipment notes, and item-level handling guidance.

Current status: active and recently refreshed. The inspected prep document showed 72 items, 3,125 singles, 13 dangerous-goods items, and 59 standard items.

Main sources: prep document JSON, prep requirements JSON, order-form artifacts, Amazon prep requirement reads, and local overrides.

Relationship: downstream of the order form; validates physical prep realities before shipment.

Escalate when prep method seems wrong, dangerous-goods status looks inconsistent, or Amazon prep guidance differs from local expectation.

Ask Fergus: “Is this Amazon prep guidance current, or is a manual pack/prep override controlling this row?”

Workflow drill

Pick one product. Trace it through:

1. Warehouse Inventory: does Brent physically have it?
2. SKU Mapping: what ASIN, SKU, FNSKU, and doTERRA product ID are connected?
3. Restock Dashboard: is it recommended for order?
4. Order Form: did warehouse stock reduce the order quantity?
5. Prep & Pack: how should it be prepped and shipped?

If those five disagree, do not assume any tile is wrong. Identify whether the mismatch is timestamp, mapping, warehouse section, previous-order reserve, or prep override.

End of module 01.