Model Data Exploration Guide

Overview

This guide is a companion to the eWAVE User Guide — that guide explains what each concept means; this one walks you through doing it, end to end, in a fresh Test company. Follow the sections in order — each step's output (an ASN, an LPN, an order, a wave) feeds the next one.

Sample Warehouse Layout

Every location you create in this walkthrough mirrors the reference four-rack distribution center below. Recreate it exactly to follow the guide step-by-step, or treat the codes as a template and substitute your own.

Four-rack distribution center simulation — the reference layout this guide's Test-company location data is modelled on.

Zones

Racks & Location Codes

Other Reference Points

Location Code Settings

Under eWAVE Location code segment settings, decide which of the six barcode segments your warehouse uses — Area, Zone, Aisle, Rack, Level, Bin — and how many characters each one is. For the sample layout, the codes are <Aisle/Bay><Rack><Level> (e.g. 101A01), so enable Aisle, Rack, and Bin/Level and leave Area/Zone off if you don't need that extra granularity.

Location Types & Areas (SKU vs. LPN)

eWAVE ships 13 seeded location types you'll reuse rather than rename — the ones relevant to this walkthrough are inventory, receiving_dock, shipping_dock, packing, and vehicle. You don't configure "an LPN area" or "a SKU area" on the type itself — tracking type (SKU or LPN) and allocation type are set per location range when you generate locations in the next step. A rack can be all-SKU, all-LPN, or split into ranges of each.

Add Locations Wizard — Generate the Racks

This bulk wizard is how you'll create Racks A–D in one pass each, rather than one location at a time.

1. Location type — leave as inventory.
2. Tracking type & Allocation type — choose SKU for a shared-slot rack (many LPNs of the same product can share the location) or LPN for a single-container-per-slot rack. This choice is what makes a range a "SKU area" or "LPN area."
3. On the Location Range page, fill only the segments you activated in Settings. To reproduce Rack A: From Aisle 101, To Aisle 102, From Rack A, To Rack A, From Bin 01, To Bin 07. Repeat the wizard for Racks B, C, and D using the codes from the layout table above.
4. Capacity page (optional) — set Maximum weight, Maximum volume, Maximum quantity, Maximum no of cases if you want capacity checks enforced.
5. Groups page (optional) — assign a Putaway group / Allocation group / Replenish group if this rack range should be targeted by a location-group rule line (see Check the Putaway Rule).
6. Click Confirm. Repeat for the Receiving dock (receiving_dock type, code SHIP01-style single location) and Shipping dock (shipping_dock type, SHIP01).

Vehicles & Packing Station

Neither of these is a separate setup screen — both are ordinary ewave.locations records distinguished only by their Location Type:

• Vehicles / carts — run the Add Locations wizard again with Location type = vehicle to create VH001–VH003. These are what the mobile Replenishment Picking screen's "Scan Vehicle/Cart" step scans against.
• Packing Station — create one location with Location type = packing (PCK001). Then decide whether pickers are routed there automatically: open Configuration → Settings → "Manage parameters" and, on the relevant Pick Orders context-parameter record, set packing_station = y ("System leads user to packing station") or n ("User decides when to go to packing station").

Product

Fill in the standard Odoo product fields (name, barcode, unit of measure), then open the eWAVE tab added to the product form:

For this walkthrough, leaving all three rule fields blank is fine — the walkthrough uses the seeded default rules XPUT000 / XFUL000 / XRPL000.

Vendor & Customer

These menu items open the standard Odoo Contacts screens — eWAVE adds no extra fields to res.partner. Create one vendor (you'll receive an ASN from them) and one customer (you'll ship an order to them).

3. Receive Your First Product — Create a SKU-Level ASN (Desktop)

1. Set ASN type to SKU (radio buttons on the form).
2. Select your Vendor.
3. Add an ASN line: your product and an expected quantity.
4. Save, then click Initiate in the header. Status moves from 10 Created to 20 Initiated — the ASN is now ready to receive against.

4. Receiving Using a Mobile Device

Scan or enter the ASN reference from step 3, then scan the product and quantity (capturing batch/lot/serial/expiry if your context parameters require them). Confirm — this creates a new LPN at status 10 Received without putting it away, so you can inspect the putaway rule before it moves.

5. Check the Putaway Rule

Open the seeded XPUT000 record ("Putaway Move Reference") — or your product's own Putaway rule if you set one. Review its rule lines: each is a Reference location, Exact location, Location range, or Location group line, evaluated in priority order. This is the rule the four-pass cascade (single-SKU → mixed-SKU, each with/without a location hint) will apply in the next step — see Putaway in the full User Guide for the algorithm diagram.

6. Putaway to a SKU Location

1. Scan the LPN created in step 4.
2. The engine resolves a destination using the rule from step 5 — for a SKU-tracked slot in Rack A, expect something like 101A01.
3. Scan/confirm the suggested location.
4. LPN status moves to 30 At location. If the destination is SKU-tracked and another LPN of the same product is already there, eWAVE merges the two LPN detail records automatically.

7. Create Your First Outbound Order

1. Set Customer (partner_id) and, if different, the freeform ship-to address fields.
2. Add an order line: the same product you received, quantity ≤ what you putaway.
3. Save. The order starts at status 10 Open.

8. Check the Fulfillment Rule

Open XFUL000 ("Fulfillment Move Reference") — this governs which locations the wave allocates from. Separately, open eWAVE → Shipping → Fulfillment rules and run wave — the same screen manages both reusable Wave Run Rules (status 00) and the actual wave executions generated from them. Create or confirm a rule record here before running a wave in the next step.

9. Run the Wave — Without Auto Packing or Routing

On your Wave Run Rule record, the three pipeline stages are controlled by sequence fields, not simple checkboxes:

Select your order (via the order filter/domain field), then click the "Run wave" button (only visible while wave_status = 00). You'll see a confirmation that the request was submitted to the background job queue — a new run record is created at wave_status = 10 and picked up by the ewave: Run inventory fulfilment for outbound orders cron, which runs every 10 minutes.

10. Check the Allocation Status

The default view filters to "Open allocations." Find the allocation record created by your wave and watch its status progress: Open → In Picking → On Vehicle → On Hold → Completed (or Deleted if cancelled).

11. Pick the Order Using the Mobile Device

1. Scan Vehicle/Cart — e.g. VH001.
2. Scan Start Location.
3. Scan Pick Location — the location the allocation points to (Rack A, if that's where you put it away).
4. Scan LPN.
5. Scan Product / Qty — governed by the scan_each context parameter (y = scan every unit, n = scan once and enter quantity).

Confirming the pick updates the allocation to On Vehicle (or the next stage) automatically.

12. Check Inventory Status — LPN View & Transaction Log

Open Inventory by LPN, find your LPN, and confirm its status and current location reflect the pick. Click its History button (or open Transactions history directly — it defaults to an inventory-movement filter) to see the full chain of transaction records this walkthrough has generated so far: LPN created, received, putaway/located, and picked.

13. Pack the Order — Non-Cubed Mobile

Scan or generate a carton number, then manually assign the picked items to the carton. Confirm to pack — this writes 7001 Carton created and 7003 Carton packed transaction records (see Packing in the User Guide for the full carton lifecycle table).

14. Enter Weight & Route

Scan the carton, enter its Weight, and select a Ship via (route/carrier service). If you'd rather do this from a desk, the same fields are exposed in eWAVE → Configuration → Debug → Ship and Manifest Wizard data as carton_id, weight, and ship_via_id.

15. Wait for the Weigh & Manifest Background Job

Entering weight/route doesn't ship the carton immediately — it queues a record (record_status Waiting/Valid/Error) for the ewave: Run weigh shipment and manifest cartons cron, which runs every 10 minutes and generates/updates the Shipment and Manifest records.

16. Create a Load and Assign a Dock Door

Set the Dock door field (e.g. SHIP01). Save — the load starts at 10 Open and moves to 20 At Dock once the door is assigned.

17. Load the Carton Using the Mobile Device

Depending on the load_number context parameter, you'll position by dock or by load — scan accordingly, then scan the carton from step 14 to load it onto the trailer.

18. Close the Load

Closing sets load_status = 80 Load Closed, clears the dock door assignment (freeing it for the next load), and logs a closing transaction.

19. Close the Manifest

Sets manifest_status = 80.

20. Close the Shipment

eWAVE validates the shipment is actually ready to close (carton loaded, manifest closed, etc.) before setting shipment_status = 80 — if something's missing, you'll get a notification explaining what, rather than a silent failure.