Glossary
The words this business uses that mean something specific here. A term is defined once, gets a
stable ID, and is referenced from every entry that relies on it — the same discipline the rules
themselves follow (CONVENTIONS.md §4).
It exists because a shared word carrying an unshared meaning is the most expensive kind of misunderstanding: a new starter reads "ship complete" and guesses, a developer reads it and guesses differently, and an AI agent asked about it will guess most confidently of all. A rule can be precise and still be misread if the words inside it are not pinned down.
How to read an entry here
| Column | What it holds |
|---|---|
| Term | The word as people actually say it, plus the aliases it travels under |
| What it means | Plain English. No field IDs, no script names — the same bar as the business reading of a rule |
| Why it matters | What changes because of it, and what goes wrong when it is misread |
| Rules | Every rule that depends on the term |
The rules of this file
- Term IDs are immutable.
LI-TERM-SHIP-COMPLETEstays that ID even if the business renames the term tomorrow. The slug is an identifier, not a label — it is readable so that aterms:list means something at a glance, and it is never rewritten to match new wording. - Never invent a meaning. A term nobody has defined is left blank and renders as needs
confirming. That is honest and actionable; a plausible guess is neither, because nobody goes
back to check the ones that look finished (
WORKING_AGREEMENT.md§4). - Definitions are restated from the entries, not invented for this file. Where a definition was taken from a rule's business reading, that rule is named. Where no entry defines the term, the meaning is left empty on purpose.
- Nothing here is confirmed yet. Every term below is marked unconfirmed, because the definitions
were derived from the entries rather than agreed by a person. Confirming them is one pass by
someone who knows the business — not a per-term interrogation
(
WORKING_AGREEMENT.md§4).
Terms with no definition at all
These are used in the rules and have never been written down anywhere. They are the reason this file exists, and they are the shortlist for that confirmation pass:
- Full Service — one of the three service levels; what it includes is unrecorded.
- Made To Order 1 and Made To Order 2 — two adjacent rungs of the lead-time ladder, with nothing recorded about what separates them.
- End Of Line and Seasonal Only — treated identically by two rules, never defined.
- Notice period — an input to every ship date.
Adding a term? Copy an existing block, keep confirmed: false until a person has agreed the
wording, and add its ID to the terms: list of every entry that leans on it.
All terms
69 terms · 8 with no recorded meaning. Every term is unconfirmed until a person agrees the wording.
| Term | What it means | Why it matters | Rules |
|---|---|---|---|
Ship completealso: Ship Whole Order · SWO · send all togetherLI-TERM-SHIP-COMPLETE |
An order that must leave the warehouse as one delivery — every line together, or nothing. The opposite is an order whose parts can go out as stock lands. | It decides which of the two piles an order joins, and therefore which automation handles it. A ship-complete order waits until every item across every linked order is in stock, so one missing part holds the whole order. | Which pile an order goes inLI-BL-FUL-001 Orders that travel togetherLI-BL-FUL-002 |
Flow 1also: nswo · Non-Ship-Whole-Order · send as it's readyLI-TERM-FLOW-1 |
The first of the two shipping runs. It handles orders whose parts may ship as stock lands, and processes each order independently. | Flow 1 runs before flow 2. An order can be promoted out of flow 1 into flow 2 if it turns out it must travel with another order. | Which pile an order goes inLI-BL-FUL-001 Orders that travel togetherLI-BL-FUL-002 |
Flow 2also: swo · Ship-Whole-OrderLI-TERM-FLOW-2 |
The second shipping run. It handles orders that must arrive in one go, and merges related orders so they travel together. | Always handled second, and only once every item across the linked orders is in stock. | Which pile an order goes inLI-BL-FUL-001 Orders that travel togetherLI-BL-FUL-002 |
Ship-together groupalso: orders that travel together · merged groupLI-TERM-SHIP-TOGETHER-GROUP |
Two or more orders from one purchase that are treated as a single delivery. An order pointing at another it must ship with pulls that order — and anything they chain to — into the group. | The same courier and the same dates are written to every order in the group, and the latest requested date across the group applies to all of them. If any item in the group is out of stock, nothing is booked. | Orders that travel togetherLI-BL-FUL-002 |
Held for reviewLI-TERM-HELD-FOR-REVIEW |
An outcome, not an error. The automation has decided it cannot safely choose, so the order is set aside for a person rather than being booked. | Held orders do not progress until someone acts on them. They are the automation working correctly, and the queue is the signal that a rule needs a human. | Picking the courierLI-BL-FRT-001 Picking the dayLI-BL-FUL-003 |
Ready orderLI-TERM-READY-ORDER |
An order that has passed every eligibility test: paid in full, not on hold, not already booked or approved or closed, no drop-ship items, goods are Standard or 2-Man, no ship date already set in the past, and at least one item still to send. | Only ready orders enter either flow. An order failing any one test is simply not picked up — it is not held, flagged or reported. | Which pile an order goes inLI-BL-FUL-001 |
Courier service levelalso: service levelLI-TERM-SERVICE-LEVEL |
The delivery service the customer paid for at checkout — Standard, 2-Man or Full Service. | It selects which list of couriers is tried, and in what order. It is the first thing the courier decision reads. | Picking the courierLI-BL-FRT-001 |
2-Manalso: Two Man · two-person deliveryLI-TERM-TWO-MAN |
A delivery that needs two people to carry the goods into the property. Items are individually marked as needing it. | One 2-Man item upgrades the whole order to 2-Man, even if the customer paid for Standard — because one heavy item makes the whole delivery a two-person job. | Picking the courierLI-BL-FRT-001 |
Full ServiceLI-TERM-FULL-SERVICE |
needs confirming | One of the three service levels, and the only one offered on ship-complete orders alongside 2-Man. What it includes beyond a 2-Man delivery is not documented anywhere in the registry. | Picking the courierLI-BL-FRT-001 |
LinehaulLI-TERM-LINEHAUL |
The long-distance leg between cities, run on a fixed weekly schedule, before a local courier makes the final delivery. | Interstate orders wait for the next departure, which is why an interstate ship date can sit days after the order is otherwise ready. Today the departures are fixed — Tuesday for Brisbane, Thursday for Melbourne. | Picking the dayLI-BL-FUL-003 |
Life truckalso: Life courier · own fleetLI-TERM-LIFE-TRUCK |
Life Interiors' own delivery vehicles, as distinct from a third-party courier. | Only Life trucks are capacity-checked and linehaul-scheduled. A Life truck delivery to any state other than NSW, ACT, QLD or VIC is not supported and is left for review. | Picking the dayLI-BL-FUL-003 |
CBMalso: cubic capacity · cubic metres · volumeLI-TERM-CBM |
Cubic metres — the volume measure used for goods and for how much a truck run can hold. | Cubic capacity is the hard limit on a truck run. An order that does not fit the remaining capacity for a day is pushed to the next day that fits. | Picking the dayLI-BL-FUL-003 One shipment, one truckloadLI-BL-FRT-002 |
Postcode coverageLI-TERM-POSTCODE-COVERAGE |
The list of postcodes a given courier will deliver to. Each courier in the service level's list is checked against the delivery postcode in turn; the first that covers it wins. | If no courier covers the postcode, the order falls back to whatever the customer picked at checkout — or is held, if that pick was "to be confirmed". | Picking the courierLI-BL-FRT-001 |
To Be Confirmedalso: TBCLI-TERM-TO-BE-CONFIRMED |
A placeholder value where a real courier would normally sit — the customer's checkout selection when no carrier has actually been chosen. | It is the difference between a fallback and a hold. A real checkout pick is honoured when no courier covers the postcode; "to be confirmed" means nobody has chosen a carrier, so a person must. | Picking the courierLI-BL-FRT-001 |
Notice periodLI-TERM-NOTICE-PERIOD |
needs confirming | One of the three inputs to the ship date, alongside the customer's requested date and truck capacity. Taken to mean the minimum warning a courier needs before collection, but the registry does not state it and it has not been confirmed. | Picking the dayLI-BL-FUL-003 |
Drop shipLI-TERM-DROP-SHIP |
Stock that ships to the customer directly from the supplier, without passing through a Life Interiors warehouse. | Drop-ship items make an order ineligible for courier approval altogether. On the storefront they change the wording of the promise from "our warehouse" to "our partners warehouse". | Which pile an order goes inLI-BL-FUL-001 The lead-time ladder, and the words the customer readsLI-BL-INV-006 |
The lead-time ladderalso: the ladderLI-TERM-THE-LADDER |
The ordered list of conditions that decides what a product's delivery promise says. Each product is tested against the rungs in order and takes the first one that fits; nothing further is considered once a rung matches. | It is the whole customer-facing promise in one structure. A product matching no rung at all has nothing written — which is a known defect, not a decision. Since 2026-08-18 rung 1 counts Sydney stock only and never bonded, while rung 2 counts unallocated bonded stock and is dated from the resolved Sydney landing date rather than the purchase order. | The lead-time ladder, and the words the customer readsLI-BL-INV-006 Bonded stock on hand, and paying off the backorder firstLI-BL-INV-011 |
Lead-time bandalso: dispatch band · the bandLI-TERM-LEAD-TIME-BAND |
The wait is always published as a range, never a date — one of twenty-three bands from "2 - 3 days" through "44 - 48 weeks". Anything beyond forty-eight weeks becomes "Please contact showroom for lead time". | A calculated number of weeks is rounded into a band before the customer ever sees it, so the published promise is deliberately coarser than the number behind it. | The lead-time ladder, and the words the customer readsLI-BL-INV-006 |
Arrival windowLI-TERM-ARRIVAL-WINDOW |
The span shown to a customer when stock is on the way — the expected arrival date plus seven days. | It is a fixed one-week spread applied to a single date, not a real delivery estimate. The date it is built on is the resolved Sydney landing date, not the purchase order's date. For a kit, the window is taken from the latest component arrival date. | The lead-time ladder, and the words the customer readsLI-BL-INV-006 A kit's promise is its slowest componentLI-BL-INV-007 Bonded stock on hand, and paying off the backorder firstLI-BL-INV-011 |
The three sentencesalso: in-stock message · arrival-window message · out-of-stock messageLI-TERM-THREE-SENTENCES |
Every product carries three separate published sentences — what happens normally, what happens when stock is on the way, and what happens when it is out of stock. Each is stored and published separately. | They are the actual words a customer reads before spending money. Downstream, a kit's promise is worked out by reading a wait back out of these sentences rather than from a number. | The lead-time ladder, and the words the customer readsLI-BL-INV-006 A kit's promise is its slowest componentLI-BL-INV-007 Publishing to Shopify — product or variantLI-BL-INV-009 |
Next Available Receive DateLI-TERM-NEXT-AVAILABLE-RECEIVE-DATE |
The date the next sellable stock of a product is expected to land in Sydney, written onto the product itself. Since the September 2026 rebuild it is the same value as the first arrival. | Everything later in the lead-time chain is built on it, so a wrong date here becomes a wrong promise on the website. The older meaning — one date per warehouse, with a separate bonded date of the same name — was retired on 2026-09-18, along with the defect (LT1-D1) where writing one warehouse's date cleared the other's. A separate bonded field still exists and means something different: the raw Vietnam date, with no transit added. Flow 2 may still show a customer an earlier date than this one when bonded stock on hand lands sooner, so the two can legitimately disagree. | Which supply counts, and when it lands in SydneyLI-BL-INV-005 The first and second arrivalLI-BL-INV-014 The lead-time ladder, and the words the customer readsLI-BL-INV-006 Bonded stock on hand, and paying off the backorder firstLI-BL-INV-011 |
Receive By DateLI-TERM-RECEIVE-BY-DATE |
The date on a purchase order by which incoming stock is expected to be received. | It is the raw input the whole chain starts from — read off the purchase order and copied onto the product as its Next Available Receive Date. | Which supply counts, and when it lands in SydneyLI-BL-INV-005 |
Sellable quantityalso: still free to sell · unallocated remainingLI-TERM-SELLABLE-QUANTITY |
How many units on one line of incoming stock could still be promised to a new customer: units still to be received, less the units NetSuite has already matched to customer orders, never below zero. | It is the gate on every arrival date. A line with no sellable quantity gets no date, however soon it lands, because every unit on it is already spoken for. Backorders NetSuite has not yet matched to a line are deliberately NOT deducted, so the figure agrees with what NetSuite shows on the order rather than with the warehouse's net position — which is why it can differ from the website's Quantity On Order. | Which supply counts, and when it lands in SydneyLI-BL-INV-005 The first and second arrivalLI-BL-INV-014 |
First arrivalalso: 1st PO · Receive Date (1st PO) · next available receive dateLI-TERM-FIRST-ARRIVAL |
The earliest date sellable stock of a product is expected to land in Sydney, with the number of units on it, taken from whichever supply source lands soonest. | It is the date the customer-facing promise is built from, and the one value in the chain that reaches a shopper. Its quantity is for buying and sales, and is a different figure from the Quantity On Order shown on the website. | The first and second arrivalLI-BL-INV-014 The lead-time ladder, and the words the customer readsLI-BL-INV-006 |
Second arrivalalso: 2nd PO · Receive Date (2nd PO)LI-TERM-SECOND-ARRIVAL |
The next date sellable stock is expected to land in Sydney after the first arrival, with the number of units on it. | It is what lets sales answer "and after that?" without opening NetSuite, and what lets buying see whether a second shipment is close enough to matter. Nothing downstream turns it into a customer promise. | The first and second arrivalLI-BL-INV-014 |
Bonded transitalso: the 35 days · Vietnam to SydneyLI-TERM-BONDED-TRANSIT |
The time stock takes to move from the bonded warehouse in Vietnam to Sydney, treated as a flat 35 days. | It is what turns a bonded date into a Sydney date, and it is the difference between stock we own and stock we can sell. It is applied to a bonded purchase order's Vietnam date, and to bonded stock on hand counted from today — but never to a transfer order, whose own expected receipt date already accounts for it. The 35 is hard-coded in two separate scripts, which must change together. | Which supply counts, and when it lands in SydneyLI-BL-INV-005 Bonded stock on hand, and paying off the backorder firstLI-BL-INV-011 |
Stale supplyalso: overdue source · more than a fortnight lateLI-TERM-STALE-SUPPLY |
An incoming source whose expected date is more than 14 days in the past. It is treated as not coming, and the next source takes its place. | A date a fortnight gone is not a date, it is a stalled shipment, and promising it to a customer promises something nobody expects. Dropping it means the product still gets a promise — a later and more honest one — rather than no promise at all. | The first and second arrivalLI-BL-INV-014 |
Bonded nettingalso: spare bonded stockLI-TERM-BONDED-NETTING |
Paying down a warehouse's existing backorder with bonded stock before any of that stock can be promised to a new customer. Stock on hand is used first, then stock on order; only what survives is treated as sellable. | Sydney's on-order figure already has backorders netted out of it, so a negative figure means stock has been sold that we do not have. Bonded stock covers that debt first. Ordinary items net at item level; kits net per component, because one component's spare stock cannot cover another component's shortage. | Bonded stock on hand, and paying off the backorder firstLI-BL-INV-011 Bonded stock is netted per component, and never guessed into a Sydney dateLI-BL-INV-012 |
Resolved Sydney landing dateLI-TERM-RESOLVED-SYDNEY-LANDING-DATE |
The earlier of two competing dates — the first arrival written by flow 1, and spare bonded stock on hand dated at today plus 35 days. | From V3.1 (2026-09-21) flow 1's date is passed through untouched rather than recalculated, and flow 2 contributes only the one arrival flow 1 structurally cannot see: bonded stock on hand, which is a stock balance with no order line behind it. Because the earlier of the two wins, the date a customer reads can be earlier than the first arrival held in NetSuite. The two are answering different questions — "the next documented arrival" and "the next arrival of any kind" — and are expected to disagree on items with spare bonded stock. | Bonded stock on hand, and paying off the backorder firstLI-BL-INV-011 The lead-time ladder, and the words the customer readsLI-BL-INV-006 The first and second arrivalLI-BL-INV-014 |
OversoldLI-TERM-OVERSOLD |
More units committed to customers than exist or are inbound, showing as a negative on-order figure for the warehouse. | Before bonded netting existed, a negative figure was published straight to the storefront. An item still oversold after all bonded stock is applied is not reported anywhere — see defect LT2-D11. | Bonded stock on hand, and paying off the backorder firstLI-BL-INV-011 |
Arrival-date gateLI-TERM-ARRIVAL-DATE-GATE |
A date is published only when a customer could act on it — the kit has sellable stock, or it can be back-ordered. If neither is true, both dates are cleared and the customer is told to contact the showroom. | Without it, a kit whose every inbound unit is already committed to existing orders would still advertise an arrival date to new customers. | Bonded stock is netted per component, and never guessed into a Sydney dateLI-BL-INV-012 |
Supply typeLI-TERM-SUPPLY-TYPE |
The classification that says how a product is supplied — In-Store Only, Made To Order 1, Made To Order 2, End Of Line, Seasonal Only, Drop Ship In-Stock Only and Drop Ship Seasonal Item among them. | It selects which rung of the ladder a product lands on, and it is one of the main things deciding whether the storefront will accept a backorder. A kit carries its own supply type, independent of its components' — read for the first time by LI-BL-INV-013. | The lead-time ladder, and the words the customer readsLI-BL-INV-006 Whether an out-of-stock item can still be orderedLI-BL-INV-008 Whether a kit can be bought out of stockLI-BL-INV-013 |
In-Store OnlyLI-TERM-IN-STORE-ONLY |
A product that can be bought in a showroom but not shipped. Where a showroom holds stock the customer is told it is available for in-store purchase there. | It short-circuits the ladder entirely — no lead time is produced at all — and with nothing on order it also blocks backorder, because the item cannot be shipped. | The lead-time ladder, and the words the customer readsLI-BL-INV-006 Whether an out-of-stock item can still be orderedLI-BL-INV-008 |
Made To Order 1LI-TERM-MADE-TO-ORDER-1 |
needs confirming | Rung 5 of the ladder, immediately above Made To Order 2. Both take the supplier's stated lead time, and the registry does not record what distinguishes one from the other — so the ordering between them cannot currently be explained to anyone. | The lead-time ladder, and the words the customer readsLI-BL-INV-006 |
Made To Order 2LI-TERM-MADE-TO-ORDER-2 |
needs confirming | Rung 6 of the ladder, immediately below Made To Order 1. See that term — the difference between the two is not documented. | The lead-time ladder, and the words the customer readsLI-BL-INV-006 |
End Of LineLI-TERM-END-OF-LINE |
needs confirming | Rung 7 of the ladder. A product on it is given no number at all — the customer is told to contact the showroom — and with nothing on order it is refused backorder. Understood to mean a discontinued product, but the registry does not say so. | The lead-time ladder, and the words the customer readsLI-BL-INV-006 Whether an out-of-stock item can still be orderedLI-BL-INV-008 |
Seasonal OnlyLI-TERM-SEASONAL-ONLY |
needs confirming | Treated identically to End Of Line on the ladder and in the backorder decision, but what makes a product seasonal — and whether it returns — is not documented. | The lead-time ladder, and the words the customer readsLI-BL-INV-006 Whether an out-of-stock item can still be orderedLI-BL-INV-008 |
BackorderLI-TERM-BACKORDER |
Allowing a customer to buy something that is not currently in stock, on the promise that it will be fulfilled when stock arrives. | Commercially the most dangerous flag in the chain. Allowing it wrongly takes money for stock that may never come; refusing it wrongly turns away a sale that could have been fulfilled. Physical stock in the second warehouse overrides every other consideration and always allows it. Kits are decided separately from 2026-08-28 under LI-BL-INV-013, on two gates rather than one — every component must allow it, and so must the kit's own supply type. | Whether an out-of-stock item can still be orderedLI-BL-INV-008 Whether a kit can be bought out of stockLI-BL-INV-013 |
The four product listsalso: Local · Imported · Rugs · Item SimpleLI-TERM-PRODUCT-LISTS |
Lead-time flow 2 runs over four separate lists of products — Local, Imported, Rugs and Item Simple — one after another. They are four categories of product, not slices of one list, and all four are handled by identical logic. | Item Simple is the list whose products never reach the storefront, because they are marked as neither a product nor a variant. What puts a product into one list rather than another is not documented. | The lead-time ladder, and the words the customer readsLI-BL-INV-006 Publishing to Shopify — product or variantLI-BL-INV-009 |
Business dayLI-TERM-BUSINESS-DAY |
When comparing waits written as sentences, a business day is converted to 1.4 calendar days. | It is how a kit decides which of its components is slowest when their promises are worded in different units. The 1.4 figure is a convention inside the logic, not a calendar calculation. | A kit's promise is its slowest componentLI-BL-INV-007 |
Kitalso: assembly · setLI-TERM-KIT |
A product sold as one thing but made up of several component items — a bed that arrives as three boxes. | A kit is as slow as its slowest member and as scarce as its scarcest member. Its promise and its stock figures are both rolled up from its components rather than held on the kit itself. Bonded stock is netted per component and never at kit level, because one component's spare stock cannot cover another's shortage. | A kit's promise is its slowest componentLI-BL-INV-007 A kit's stock is its scarcest componentLI-BL-INV-010 Bonded stock is netted per component, and never guessed into a Sydney dateLI-BL-INV-012 |
Kit memberalso: componentLI-TERM-KIT-MEMBER |
One of the items a kit is made of. Each carries its own promise and its own stock figures, worked out by the ordinary inventory-item logic. | The kit reads its members; it never has figures of its own. If any member has no promise at all, the whole kit falls back to "please contact showroom". | A kit's promise is its slowest componentLI-BL-INV-007 A kit's stock is its scarcest componentLI-BL-INV-010 |
Showroom stockLI-TERM-SHOWROOM-STOCK |
Stock held in a physical showroom rather than a warehouse, counted per showroom. | For a kit it is rolled up as the lowest figure across components, per showroom — so a kit only counts as being in a showroom if every part of it is. | The lead-time ladder, and the words the customer readsLI-BL-INV-006 A kit's stock is its scarcest componentLI-BL-INV-010 |
Sydney WarehouseLI-TERM-SYDNEY-WAREHOUSE |
The main Sydney warehouse, location 11 — the one orders are fulfilled from. | It is the warehouse the replenishment run tops up, and one of the two whose arrival dates feed the customer promise. | Which supply counts, and when it lands in SydneyLI-BL-INV-005 What gets replenished, and how muchLI-BL-INV-001 |
Sydney Overflowalso: OverflowLI-TERM-OVERFLOW |
A second Sydney warehouse, location 23, holding stock that does not fit the main one. It is reported as Sydney, because it is still Sydney. | It is drained before Bonded when Sydney is short, because moving stock from it is a local truck movement of about a week rather than a shipment from overseas. | Overflow before BondedLI-BL-INV-003 Which supply counts, and when it lands in SydneyLI-BL-INV-005 |
Bonded Warehousealso: Bonded · Bonded WH · VietnamLI-TERM-BONDED-WAREHOUSE |
The warehouse in Vietnam, location 25. Stock has to cross the water and clear into Sydney before it is sellable. | Two different transit figures are in use for the same journey, and both are documented: replenishment describes it as roughly six weeks, while the lead-time chain applies a flat 35-day allowance. Bonded is used only for whatever Overflow cannot cover, and never in the same shipment as Overflow. A product with stock coming to Bonded still loses its Sydney arrival date (defect LT1-D1). | Overflow before BondedLI-BL-INV-003 Which supply counts, and when it lands in SydneyLI-BL-INV-005 Bonded stock on hand, and paying off the backorder firstLI-BL-INV-011 Bonded stock is netted per component, and never guessed into a Sydney dateLI-BL-INV-012 |
Transfer Orderalso: TOLI-TERM-TRANSFER-ORDER |
The paperwork that moves stock from one warehouse to another. One Transfer Order is one shipment, and one shipment is one truck. | Two warehouses supplying the same shortage raise two separate Transfer Orders, because one shipment cannot come from two warehouses. | Overflow before BondedLI-BL-INV-003 Add to an open order before raising a new oneLI-BL-FUL-004 One shipment, one truckloadLI-BL-FRT-002 |
Open Transfer OrderLI-TERM-OPEN-TRANSFER-ORDER |
A Transfer Order that has been raised but not yet handled by the warehouse team, and can therefore still be added to. | Stock already on an open Transfer Order is not moved again, which is what stops the same stock being ordered every night. Once the team has handled an order it is locked and nothing more is added, so a shipment being picked cannot change underneath the warehouse. | What gets replenished, and how muchLI-BL-INV-001 Add to an open order before raising a new oneLI-BL-FUL-004 |
TruckloadLI-TERM-TRUCKLOAD |
The volume one truck can carry, and therefore the maximum size of a single Transfer Order. | A single item whose volume exceeds a truckload is split across the fewest new orders that will hold it. An addition that would overfill an open order is refused outright. | One shipment, one truckloadLI-BL-FRT-002 |
BinLI-TERM-BIN |
A physical storage location inside a warehouse, holding a quantity of one item. | Replenishment picks the smallest bin that still covers the shortage and moves the whole bin, not just the shortfall. The bin is never named on the Transfer Order — the warehouse chooses the physical bin when it picks. | Whole bins, closest fitLI-BL-INV-002 |
ShortfallLI-TERM-SHORTFALL |
What is still uncovered after every available warehouse has contributed what it can. | The automation moves whatever exists rather than waiting for full coverage, and emails the remaining gap to the inventory planner. That email is sent on every run, clean or not — it is an operational alert, not an error report. | Move what there is, flag the restLI-BL-INV-004 |
Inventory plannerLI-TERM-INVENTORY-PLANNER |
The person who receives the daily shortfall alert and sources what the warehouses could not cover. | They are the human end of the replenishment run. Without the alert, uncovered demand is invisible. | Move what there is, flag the restLI-BL-INV-004 |
Authority to Leavealso: ATL · leave unattended · safe dropLI-TERM-ATL |
The customer has told us the driver may leave the delivery in a safe place without anyone being home to receive it. | It decides whether we ask the customer to confirm the delivery date at all. An Authority to Leave delivery is told its date rather than asked to agree it — but only when nothing in the delivery needs the customer present, because a two-man or full-service delivery cannot be left unattended. | One conversation per customer per dayLI-BL-FUL-006 Authority to Leave needs no replyLI-BL-FUL-008 |
Customer Delivery Confirmationalso: CDC · delivery confirmation · confirmation stateLI-TERM-CDC |
Where a delivery has got to in the confirmation conversation with the customer — not asked yet, asked once, asked twice, agreed, or waiting on a person. | It is the state the whole conversation runs on. Its value decides which queue a delivery appears in and therefore what happens to it next, so changing it by hand moves the delivery between stages. Setting it to "Manual - Exclude from automation" takes the delivery out of automation entirely. | Which deliveries we ask aboutLI-BL-FUL-005 Two attempts, then stop askingLI-BL-FUL-007 Authority to Leave needs no replyLI-BL-FUL-008 Giving back an unconfirmed dateLI-BL-FUL-009 Confirming the date we offeredLI-BL-FUL-011 Accepting the date they choseLI-BL-FUL-013 Handing back to the teamLI-BL-FUL-014 Escalating a delivery we cannot settleLI-BL-FUL-017 |
Scheduled Delivery Datealso: SDD · delivery dateLI-TERM-SCHEDULED-DELIVERY-DATE |
The date we intend to deliver to the customer, as distinct from the ship date the goods leave the warehouse on. | It is the date quoted to the customer and the date they are agreeing to. It is also part of what groups orders into a single conversation, so two orders arriving the same day are one delivery as far as the customer is concerned. | Which deliveries we ask aboutLI-BL-FUL-005 One conversation per customer per dayLI-BL-FUL-006 Giving back an unconfirmed dateLI-BL-FUL-009 Accepting the date they choseLI-BL-FUL-013 The reminder before delivery dayLI-BL-FUL-016 |
Consignment numberalso: connote · consignment note · CN · tracking numberLI-TERM-CONSIGNMENT |
The carrier's own reference for a delivery — the number printed on the label and the only thing a carrier can be asked about. | It is the key that joins our record of a delivery to the carrier's. A delivery without one cannot be tracked at all, and one the carrier does not recognise ends every run with nothing written — usually because the consignment was created under a supplier's carrier account rather than ours. | Which deliveries we chaseLI-BL-FUL-018 What actually gets writtenLI-BL-FUL-024 |
Ship Viaalso: ship method · shipping methodLI-TERM-SHIP-VIA |
Which carrier and service a delivery was booked on. | It is what decides who gets asked where a delivery is. Ship methods are renamed often — new regions, new size bands, new prefixes — so tracking matches on the carrier's name inside the ship method as well as on the exact name. A ship method mentioning no carrier we know is skipped silently, so an unrecognised one means those deliveries are never tracked. | Which deliveries we chaseLI-BL-FUL-018 Matching a delivery to its carrierLI-BL-FUL-019 |
Item Fulfilmentalso: fulfilment · IFLI-TERM-ITEM-FULFILMENT |
The record of goods leaving the warehouse against an order — what was sent, when, and on which carrier. | It is the record delivery status is kept on, so it is where Customer Service looks to answer "where is my order". One order can have several, and each is tracked separately, because each can be on a different carrier with its own consignment number. | Which deliveries we chaseLI-BL-FUL-018 What actually gets writtenLI-BL-FUL-024 |
Delivery statusalso: courier status · tracking statusLI-TERM-DELIVERY-STATUS |
Where a delivery has got to, on a fixed list of twenty stages running from manifested through to delivered, returned, or held at one of our own depots. | It is the answer to the most common question Customer Service is asked. The list is ours, not any carrier's, so every carrier's wording has to be translated into it — and wording nothing recognises leaves the delivery sitting on its last known stage rather than being guessed at. | Turning the carrier's words into our statusLI-BL-FUL-021 Never overwrite something good with nothingLI-BL-FUL-022 Never move a delivery backwardsLI-BL-FUL-023 What actually gets writtenLI-BL-FUL-024 |
Item Stagealso: the stage · item status · supply chain stageLI-TERM-ITEM-STAGE |
The short message carried on each open sales order line saying where that item is up to — "Ready to be shipped", "On its way to our warehouse", "Delayed - Item is in production", and a dozen others. It is per line, never per order, so items on one order can each say something different. | It is the customer-facing answer to "where is my order", and it is also read by the automation that sends delay emails, so a wrong value does not just misinform — it can send the wrong email. It is rewritten once a day overnight, which means a message that looks stale during the working day is usually waiting for tonight's run rather than broken. | What the order line says on its ownLI-BL-CMS-001 What the shipment's progress saysLI-BL-CMS-003 When we bother writing it backLI-BL-CMS-004 |
Delay Commsalso: delay communication · delay email sent · delay call scheduledLI-TERM-DELAY-COMMS |
A record on a sales order line of whether the customer has been told about a delay — either a delay email was sent, or a delay call was scheduled. Blank means neither has happened. | It is the only thing that makes an item's message read "Delayed". Nothing about how late the item actually is enters into it, so an item months overdue with nothing recorded here still reads as if it is on track, and an item recorded as delayed keeps saying so until its shipment moves on. | What the shipment's progress saysLI-BL-CMS-003 |
Stage 2 delay call requestalso: Stage 2 · delay call request · Stage 2: Delay Call Request · delay call scheduledLI-TERM-DELAY-CALL-REQUEST |
The internal request raised for Customer Service to telephone a customer about a second or further delay to an item they have ordered. One request covers one order, however many of its items are late. | It is work for a person, not a message to the customer — nothing is sent when it is raised, and the customer hears nothing until someone calls. "Stage 2 has been raised" is routinely read as "the customer has been told", and those are different states. It is also the point at which the order's lines are recorded as having been called about, which is what makes their customer-facing message able to read "Delayed". | Which delays are handled by a callLI-BL-CMS-005 One request per order, every late item on itLI-BL-CMS-006 Who the call lands withLI-BL-CMS-007 Recording the call, and not asking twiceLI-BL-CMS-008 What stops, and what carries onLI-BL-CMS-009 |
Delay Ship Datealso: last delay comm date · last communicated ship dateLI-TERM-DELAY-SHIP-DATE |
The ship date last communicated to the customer about a sales order line — what they were told the last time anyone contacted them, as distinct from what we currently expect. | It is the brake on the same delay being raised twice. It is read as the "last delay comm date" an agent quotes, then overwritten with the ship date currently expected, so the gap between the two is what lets a *further* slip qualify as a new conversation while the same slip does not. Because it is a snapshot of what was said, it is normal and correct for it to disagree with the Expected Ship Date on the same line. | One request per order, every late item on itLI-BL-CMS-006 Recording the call, and not asking twiceLI-BL-CMS-008 |
Stage 1 delay notificationalso: Stage 1 · delay email · delay email sent · delay SMSLI-TERM-DELAY-STAGE-1 |
needs confirming | The first contact a customer gets when an item slips, and the thing Stage 2 assumes has already happened. What it actually sends is not recorded anywhere in this registry: the wording lives outside version control, and NetSuite carries two live script searches for it — one for SMS and one for Klaviyo — plus an inactive Dotdigital one, with nothing establishing whether both fire or which is authoritative. Until that is answered, an entry that says "the customer was already told" cannot say what they were told. | Which delays are handled by a callLI-BL-CMS-005 |
Allocated PO#also: allocated purchase order · the PO on the lineLI-TERM-ALLOCATED-PO |
The purchase order a sales order line's incoming stock has been matched to, stamped on the line so the shipment behind a customer's item can be found. | It is how supply chain traces which container or supplier order a customer is waiting on, and it is the tell that distinguishes two messages that share the same wording. It is only ever written when a purchase order was matched — never cleared — so a line can carry a stale one after a failed match. | Finding the shipment behind the stockLI-BL-CMS-002 When we bother writing it backLI-BL-CMS-004 |
Purchase Order Stagealso: PO stage · the stage the PO is atLI-TERM-PO-STAGE |
How far along an incoming purchase order is, in supply chain's own words — from "Order Placed (Local)" through "(Overseas) Currently in Production" and "(Overseas) in transit" to "Local: Order Shipped". | It is the input behind every message that describes a shipment rather than an order line. The stages are sorted into three buckets — in production, in transit, only just ordered — and the bucket, not the stage name, decides the wording the customer sees. A stage in no bucket leaves the line's message untouched, so adding a stage in NetSuite without adding it to a bucket freezes those lines silently. | What the shipment's progress saysLI-BL-CMS-003 |
Allocated supplyalso: reserved stock · earmarked against a shipmentLI-TERM-ALLOCATED-SUPPLY |
needs confirming | Taken to mean quantity on a sales order line earmarked against stock that has not arrived yet, as distinct from stock already committed in the warehouse. It is the fork in the whole item stage automation: zero sends a line down the "nothing reserved" branches, and anything above zero is what makes it go and look up a purchase order. The registry does not state its exact NetSuite definition and it has not been confirmed. | What the order line says on its ownLI-BL-CMS-001 Finding the shipment behind the stockLI-BL-CMS-002 |
Part Onlyalso: part-only item · member-only item · component itemLI-TERM-PART-ONLY |
A checkbox on an item record marking it as something sold only inside a kit, never on its own. Confirmed by the project owner on 2026-09-30: it is not a descriptive label but the **membership criterion** by which a kit component enters the lead-time chain. | An unticked component is invisible to the item flow. Its lead-time fields, its three sentences, its on-order quantity and its backorder setting all freeze at whatever they last held, and every kit containing it silently inherits those stale values. Nothing errors and nothing is logged. A component that is also a sellable product in its own right enters the chain by that route instead, which is why the gap only bites on parts that are neither. | Whether an out-of-stock item can still be orderedLI-BL-INV-008 Whether a kit can be bought out of stockLI-BL-INV-013 |
Committedalso: quantity committed · set asideLI-TERM-COMMITTED |
Stock physically in our warehouse and reserved against a particular sales order line, as opposed to stock still on its way to us. | A line whose full quantity is committed is answered immediately as "Ready to be shipped" and no purchase order is looked up at all. It is also subtracted from allocated supply when testing whether an incoming purchase order is large enough to be the one the stock is on. | What the order line says on its ownLI-BL-CMS-001 Finding the shipment behind the stockLI-BL-CMS-002 |