Overview
Luminous now stamps two date fields on purchase orders related to arrival timing:
| Field | What it means |
|---|---|
| Original ETA | The system-calculated planned arrival date, frozen at first calculation. A benchmark you can compare against later. |
| Arrival Due Date | The live, editable expected arrival date — updated by your team or forwarder as the shipment progresses. |
What triggers a calculation
Original ETA is calculated (and saved) automatically when all three of the following are set on the purchase order:
- Requested pickup / ship date — the date goods leave the supplier
- Destination warehouse — where the goods are headed
- Freight method — Air, Sea, Road, Rail, or Express
If any of these is missing, the Original ETA field stays blank until they are all present.
The calculation
Original ETA = Requested Ship Date + Calendar Days (from the matching Transit Time Matrix lane)
If the result falls on a Saturday or Sunday and the matching lane has Snap weekend enabled (the default), the date is pushed forward to the following Monday.
Per-PO override
If you enter a number in the Override Transit Days field on the PO, Luminous uses that number instead of looking up the matrix. This lets you adjust a single order without changing the shared lane settings. Weekend snapping is not applied when using an override (the service treats the override as an exact day count).
How Original ETA and Arrival Due Date are seeded
| Situation | What happens |
|---|---|
| PO created / saved with all three inputs present; Original ETA is blank | Original ETA is calculated and saved. Arrival Due Date is also filled from the same value if it is currently blank. |
| Original ETA is already set | Nothing is overwritten — the existing value is preserved as the frozen benchmark. |
| Arrival Due Date is already set (manually entered) | It is left alone — the calculation does not overwrite a date you have already chosen. |
Where to find these fields on a purchase order
On the purchase order create/edit form:
- Freight method — sets the mode used for matrix lookup
- Original ETA — read-only; shows the system-stamped date
- Override Transit Days — optional; enter a number to bypass the matrix for this order
- Arrival Due Date — the standard editable ETA field
Importing purchase orders
The PO bulk import sheet accepts three new columns:
| Column header | Description |
|---|---|
SHIPMENT_TYPE | Freight method (Air, Sea, Road, Rail, or Express) |
ORIGINAL_ARRIVAL_DATE | Frozen Original ETA. When you supply a value, the import trusts it and skips matrix calculation. Format: YYYY-MM-DD or DD-MMM-YYYY |
OVERRIDE_TRANSIT_DAYS | Per-PO transit day override |
Troubleshooting
Original ETA is blank after I saved the PO. → Check that Requested Ship Date, Destination Warehouse, and Freight Method are all filled in. Also verify that a matching lane exists in the Transit Time Matrix (Inventory → Inventory Admin → Transit Time Matrix).
I want to recalculate Original ETA after changing the freight method or pickup date. → Original ETA is a read-only field — you cannot clear or type into it directly. Instead, check the "Recalc Original ETA on save" checkbox next to the field and save the PO. This recomputes Original ETA from the current inputs. If Arrival Due Date has not been manually changed since it was seeded, it will also be updated to match; if you've already edited Arrival Due Date yourself, it's left alone.
Arrival Due Date didn't change when I expected it to. → If you had already entered an Arrival Due Date manually, the system leaves it alone. Only a blank — or not-yet-diverged — Arrival Due Date is updated from Original ETA.