Open questions

Everything the registry knows it does not know, gathered from every entry and generated on each build. It is the other half of being honest about gaps: the field registry marks a field as needs confirming, and this page carries the questions that are too big to be a field.

Why this page exists

An entry never guesses. Where something could not be established — what a saved search filters on, which team owns a chain when the numbers go wrong, whether the deployed code is the code that was read — the entry records the question instead of an answer, and publishes anyway.

That is the right call per entry and a bad one across nine of them: a question recorded on page six of a thousand-line document is not a question anyone is going to answer. Here they are one list, with who can answer where that is known.

How to read this

Open first, then answered. An answered question is kept, because the answer is the record of why the entry says what it says, and re-asking it a year later is how a registry loses time.

Who can answer is often blank. Where the entry did not record it, it is not guessed at. A question with a name against it gets answered; one without goes to whoever is reading.

38 questions open across 8 entries · 8 closed.

Open

Courier Tracking Status Update 5

Open the entry · draft

RefStatusQuestionWho can answer
CT-Q1 Open Saved search 7756's filters have not been read. Everything this entry says about scope comes from how the automation treats the rows it receives, not from the search's own definition. What makes a fulfilment appear — and whether supplier-account ship methods are already excluded — is unconfirmed. needs confirming
CT-Q2 Open The RESTlet's field whitelist is unverified. The five-field limit is documented in the repository README; the script itself is not in version control. needs confirming
CT-Q3 Open The schedule is unverified. Twice daily at 06:00 and 18:00 AEST is the README's account of an EventBridge rule that is not in version control. needs confirming
CT-Q4 Open Nothing here has been checked against production. This entry is draft for that reason. needs confirming
CT-Q5 Open The old AusPost Lambda's status is unknown. The README describes a cutover from ap-tracking-status-update that leaves both running for a period. Whether that cutover completed — and so whether two automations are writing these fields — has not been established. needs confirming

Delay Comms — Stage 2: the delay call request 8

Open the entry · draft

RefStatusQuestionWho can answer
DN-Q1 Open Which saved search feeds this automation? The search id is held in the Lambda's environment as N_SEARCHID and does not appear in the repository. The only Stage 2 script search in NetSuite is customsearch3826, "SCRIPT | DELAY | STAGE 2 | TASK | OVERSEAS | ITEM DELAY NOTIFICATION *legacy" — its name matches and it returns no rows today, but its *legacy marker sits oddly against a live automation, and its column set has not been matched against the columns the formatter reads. Until this is confirmed, every eligibility condition below is unread. Christian Sy
DN-Q2 Open What invokes the Lambda, and on what schedule? Nothing in the repository declares a trigger. From the creation times of the conversations it raises, it appears to run once a day at about 13:30 Sydney time, which is also when the Stage 1 delay emails are timestamped — but that is read off the output, not off a schedule. Julian Ayoub
DN-Q3 Open What actually makes a line eligible? Specifically: is there a Days Delayed threshold, is it restricted to overseas supply as the search name suggests, are drop-ship lines excluded, and does it require Delay Comms to already be Stage 1? All of these live in the feed search, not in the code. The code's own comment about excluding drop-ship lines does not match what it does, which suggests the exclusion was expected to be in the search. Christian Sy
DN-Q4 Open What clears or ends a Stage 2 request? Nothing in this automation resets Delay Comms, and no other documented rule writes that field. So it is not established whether a line that catches up is ever taken back off Stage 2, or whether the value simply stays for the life of the order. Phuong
DN-Q5 Open What are the note type and direction the audit log is created with, and what is the Customer Fax ID field really carrying? All three are environment values or unlabelled fields that the code passes through without using. Christian Sy
DN-Q6 Open Is a Kustomer queue set on these conversations? The code sends a queue id from its environment, but the conversation read back from production shows no queue on the record. Either the value is unset or the queue is not returned by the API. Julian Ayoub
DN-Q7 Open Was the cluster of duplicate requests on 2026-06-11 deliberate testing or a production incident? Three orders received three or four requests each within half an hour, outside the daily window. If it was testing, four customers were queued for calls they did not need. Julian Ayoub
DN-Q8 Open What does the Stage 1 delay message actually say, and which channel is authoritative? Stage 2 assumes the customer has already been told something, but the wording lives outside this repository, and NetSuite carries two live Stage 1 script searches — one for SMS (customsearch5152) and one for Klaviyo (customsearch6155) — plus an inactive Dotdigital one. Nothing read here establishes whether both fire, or what either sends. Phuong

Life Truck Delivery Date Confirmation 4

Open the entry · active

RefStatusQuestionWho can answer
DC-Q1 Open The outbound EventBridge schedule is not in any repository. The ~24 hour gap between attempts comes from how often the outbound Lambda runs, so the real cadence lives in the AWS console. needs confirming
DC-Q2 Open S1.3, the reminder, has no CI deployment and no workflow run in its repository. Its behaviour is documented from code; whether that code is the code running is unconfirmed. Treat LI-BL-FUL-016 as the least verified rule here. needs confirming
DC-Q3 Open N_SEARCHID_FINAL = '7328' appears in the escalation repo's staging config and in no production config. It may be a fourth stage that was started and parked. needs confirming
DC-Q4 Open Saved search names are not recorded — only ids. The links resolve, but if a search is renamed the name will not help anyone find it. needs confirming

Lead Time flow 2 — Inventory item lead time, and the Shopify push 8

Open the entry · active

RefStatusQuestionWho can answer
LT2-Q1 Open Is the 35-day transit allowance still right? It is a flat constant in the script, with a note that it should move to a Celigo setting if Vietnam freight becomes seasonal. Every bonded promise the customer sees rests on it. needs confirming
LT2-Q2 Open Has customer service been told the arrival date changed meaning? The script's own comment says to notify them before deploying. The field now means "lands in Sydney", not "date on the purchase order". needs confirming
LT2-Q3 Open Which locations are warehouse and warehouse2? The on-hand total adds them together. Given flow 1 treats Sydney Overflow as Sydney, these are most likely Sydney Warehouse and Sydney Overflow, but the searches would need reading to confirm it. needs confirming
LT2-Q4 Open Is the Ships In dispatch band meant to reach Shopify? It is written to NetSuite but is not one of the five metafields pushed. The three sentences, the on-order quantity and the warehouse on-hand quantity go. needs confirming
LT2-Q5 Part answered2026-09-23 What is the Item Simple list for? Partly answered 2026-09-23. A live run returns 833 items, of which 468 route to Shopify and 365 do not. Of those 365, 237 are not on Shopify at all, so the list is a mixture of storefront and non-storefront items. The remaining question is whether the 237 should be in the search at all — excluding them would cut the run and remove most of the noise LT2-D19 hides in. needs confirming
LT2-Q6 Open Is the router's branching script still needed? The router names a script function that the exported script does not define. Routing is done by the branch filters, so it appears to be a leftover. Re-checked 2026-09-23, unchanged. needs confirming
LT2-Q7 Open Should the Local and Rugs searches keep the two arrival quantities out of the Shopify payload entirely? Raised 2026-09-23. Wrapping them in a presence test (LT2-D16) stops the rejected write, but it leaves two metafields that never exist for those categories. If the storefront theme reads them, it needs to handle absent as well as zero. Nobody has checked what the theme does. needs confirming
LT2-Q9 Open Which stock does rule 1 of LI-BL-INV-008 actually mean by "the second warehouse"? The rule is written as an absolute override — the second warehouse holds stock, allowed, whatever else is true — but production disagrees for the field the name suggests. Measured 2026-09-30 across active items: of those that are End Of Line with custitem_qty_available_wh above zero, nothing on order and no supplier stock, 140 are refused and only 12 allowed. Rule 3 is winning and rule 1 is not firing on that field. On those records custitem_qty_available_gc, _syd, _mel and _bris — the showroom locations — are all zero, so rule 1 may mean one of those rather than the warehouse figure, or may be narrower than written. It is not inferred here.Why it matters: Until it is confirmed the rule promises an override the flow does not apply, which is the kind of gap nobody re-checks because the page looks finished. It is also the root of LT3-D17 on kits: raised from 396981 Noir Oval Dining Table (220cm, Black Oak), where an End Of Line Top holding 3 units refuses backorder and vetoes the whole kit. Answering it decides whether that fix belongs at item level or kit level. The Back End Team for which field the flow reads; the Buying Team for whether an End Of Line item we physically hold should be sellable when nothing more is coming.

Lead Time flow 3 — Kit item lead time, rolled up from members 2

Open the entry · active

RefStatusQuestionWho can answer
LT3-Q2 Open Is the mixed-quantity case (LI-BL-INV-010 case 2) still wanted? It is the most intricate rule in the chain and the only place the "please contact" safeguard is deliberately bypassed. needs confirming
LT3-Q4 Open How many kits does the first V3.2 run actually turn off? Gate 2 is new logic against the kit's own supply type, which nothing had read before, so the first run is the first time anyone sees the disagreement count. It should be checked against the run rather than assumed. needs confirming

Lead Time flow 1 — First and second arrival into Sydney 2

Open the entry · active

RefStatusQuestionWho can answer
LT1-Q1 Open Does saved search 7973 still report Sydney Overflow (23) as Sydney (11)? If it does, overflow movement is counted as incoming, against two confirmed rules needs confirming
LT1-Q4 Open Who built and who now maintains Lead Time: Update Next Available Receive Date v2 Sep 2026? needs confirming

Lead Time flow 4 — Original Lead Time on the sales order line 5

Open the entry · draft

RefStatusQuestionWho can answer
OL-Q1 Open What calculates the date? The candidates are all in the search — the item's arrival date, its dispatch band, the supplier's date — but which one wins, and how the order date factors in, is in the script. needs confirming
OL-Q2 Open Is an existing value overwritten? The search returns the line's current Original Lead Time, which suggests the flow compares against it. If it overwrites, the "original" promise is not original — it moves. That would undermine the entire point of the field and is the first thing to check. needs confirming
OL-Q3 Open Why does the search return several rows per line? The sample returned three rows for order S319344 line 1, identical except for the item's available and on-order quantities. Either the search joins across something, or those rows are not what they appear to be. needs confirming
OL-Q4 Open What does leadSource do here? A promise made on the website and one made in a showroom may not be the same promise. needs confirming
OL-Q5 Open Are kits handled? itemType is returned, and kits carry their lead times differently. needs confirming

Supply Chain — Item Stage: the message on every open order line 4

Open the entry · draft

RefStatusQuestionWho can answer
IS-Q1 Open What are the selection criteria on saved search 4085?Why it matters: It decides which lines are looked at at all. A line outside it keeps its message forever with no error anywhere Whoever maintains the search
IS-Q2 Open What sort order does saved search 4084 return purchase orders in?Why it matters: It decides which purchase order wins when more than one is acceptable Whoever maintains the search
IS-Q3 Open Should IS-D2's stage bucketing change?Why it matters: It changes what customers are told about overseas orders Supply chain
IS-Q4 Open Which NetSuite labels sit behind the unlabelled fields above?Why it matters: The business reading of the field registry is incomplete until they are filled in Whoever maintains the searches

Closed

Kept because the answer is the record of why an entry says what it says.

Lead Time flow 2 — Inventory item lead time, and the Shopify push 1

Open the entry · active

RefStatusQuestionWho can answer
LT2-Q8 Answered2026-09-23 Which team owns this chain when the numbers go wrong? Answered 2026-09-23. It splits by cause: Back End Team for anything technical or calculation-related, Buying Team where a purchase order carries incorrect data. The practical test is whether correcting the purchase order in NetSuite would fix it. Every defect in this entry's table is the Back End kind — with one partial exception: the 20 items under LT2-D19 need their Shopify ids recorded in NetSuite, which is a data fix, though not a Buying one. needs confirming

Lead Time flow 3 — Kit item lead time, rolled up from members 2

Open the entry · active

RefStatusQuestionWho can answer
LT3-Q1 Moot2026-09-21 What timezone does flow 3 actually run in? Moot from 2026-09-21 — flow 3 has no schedule. Flow 2 starts it, so it inherits that chain's timing rather than a clock of its own. The flow does declare Australia/Sydney, which now only affects date arithmetic inside the run. needs confirming
LT3-Q3 Answered2026-08-28 Should kits get a backorder decision? Answered 2026-08-28 — they do, here, under LI-BL-INV-013. The separate flow that used to make it is disabled. needs confirming

Lead Time flow 1 — First and second arrival into Sydney 5

Open the entry · active

RefStatusQuestionWho can answer
LT1-Q2 Answered2026-09-23 What are the PO stage values and their internal ids? Answered 2026-09-23 — read from NetSuite and recorded under Worked example — every field. needs confirming
LT1-Q3 Answered2026-09-23 Which internal team owns this when the numbers go wrong? Answered 2026-09-23. It splits by cause: Back End Team for anything technical or calculation-related, Buying Team where a purchase order carries incorrect data. Recorded in the business reading and in for_department. needs confirming
LT1-Q5 Answered2026-09-23 Does saved search 7973 sort by item? Answered 2026-09-23 — yes. It sorts by item internal id, then receive-by date, then document. That bounds LT1-D6 to at most one product per run and tells us which way it fails; both are recorded on the defect. needs confirming
LT1-Q6 Answered2026-09-23 Is dropping a stale source fixed policy? Answered 2026-09-23 — yes. Recorded in LI-BL-INV-014: the second arrival is promoted into the first slot so that everything downstream reads one field. needs confirming
LT1-Q7 Answered2026-09-23 Should the customer-facing message follow NetSuite's date? Answered 2026-09-23 — yes, the message reads the first arrival. That is the confirmed rule; the code does not always honour it, which is now defect LT2-D17. needs confirming