Integration Map

Sits beneath the Organisation Map, which is the picture; this is the detail underneath it.

Two views of how the documented logic hangs together, generated from the entries themselves every time the site is built. Nothing here is drawn by hand, so it cannot drift from the entries the way a diagram in a whiteboarding tool would.

Every rule ID links straight to the rule.

How to read this

The systems view is for orientation — which platforms each rule touches, and which flows start which. Useful for onboarding and for answering "what would this change affect?".

The field view is the one that finds problems. Integrations rarely break at the system level; they break where two of them write the same field. Every cross-flow defect found in this registry so far has been a field-level one — a field written by two rules with different meanings, a field written to a name that does not exist, a field computed and then mapped nowhere. A boxes-and-arrows diagram of systems would have shown none of them. This table shows all of them.

The gaps list is hand-maintained, and deliberately so. The generated views can only draw what is documented; on their own they would quietly imply that the rest does not exist. What is missing matters as much as what is here.

Systems and chains

EntryRulesSystemsTriggered byRuns after
Courier Tracking Status UpdateWhich deliveries we chaseLI-BL-FUL-018 Matching a delivery to its carrierLI-BL-FUL-019 Which event counts as "now"LI-BL-FUL-020 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 Finish what fits, hand the rest to the next runLI-BL-FUL-025 Proving each carrier can still be readLI-BL-FUL-026
aws-lambdanetsuiteaws-eventbridgeaws-cloudwatch
scheduled-lambda-run—
Delay Comms — Stage 2: the delay call requestWhich 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
aws-lambdanetsuitekustomeraws-ses
scheduled-lambda—
Life Truck Delivery Date ConfirmationWhich deliveries we ask aboutLI-BL-FUL-005 One conversation per customer per dayLI-BL-FUL-006 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 Reading the customer's replyLI-BL-FUL-010 Confirming the date we offeredLI-BL-FUL-011 Offering the next available datesLI-BL-FUL-012 Accepting the date they choseLI-BL-FUL-013 Handing back to the teamLI-BL-FUL-014 Replies after the conversation closesLI-BL-FUL-015 The reminder before delivery dayLI-BL-FUL-016 Escalating a delivery we cannot settleLI-BL-FUL-017
aws-lambdanetsuiteaws-dynamodbkustomeraws-end-user-messaginggoogle-sheetssupabase
scheduled-lambda-run, inbound-sms—
Lead Time flow 2 — Inventory item lead time, and the Shopify pushThe 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 Publishing to Shopify — product or variantLI-BL-INV-009 Bonded stock on hand, and paying off the backorder firstLI-BL-INV-011
celigonetsuiteshopify
flow-chainWhich supply counts, and when it lands in SydneyLI-BL-INV-005
Lead Time flow 3 — Kit item lead time, rolled up from membersA 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 Whether a kit can be bought out of stockLI-BL-INV-013 How many kits each arrival brings, and whenLI-BL-INV-015
celigonetsuiteshopify
scheduled-celigo-flowThe lead-time ladder, and the words the customer readsLI-BL-INV-006
Lead Time flow 1 — First and second arrival into SydneyWhich supply counts, and when it lands in SydneyLI-BL-INV-005 The first and second arrivalLI-BL-INV-014
celigonetsuite
scheduled-celigo-flow—
Lead Time flow 4 — Original Lead Time on the sales order lineStamp the promised lead time onto the order lineLI-BL-ORD-001
celigonetsuite
scheduled-celigo-flow—
Shipping Automation — Module 5: Courier Approval & Set Ship DateWhich pile an order goes inLI-BL-FUL-001 Orders that travel togetherLI-BL-FUL-002 Picking the courierLI-BL-FRT-001 Picking the dayLI-BL-FUL-003
aws-lambdanetsuitedetrackgoogle-sheetsaws-s3
scheduled-lambda-run—
Supply Chain — Item Stage: the message on every open order lineWhat the order line says on its ownLI-BL-CMS-001 Finding the shipment behind the stockLI-BL-CMS-002 What the shipment's progress saysLI-BL-CMS-003 When we bother writing it backLI-BL-CMS-004
celigonetsuite
scheduled-celigo-flow—
Transfer Order Automation — Daily Overflow → Sydney ReplenishmentWhat gets replenished, and how muchLI-BL-INV-001 Whole bins, closest fitLI-BL-INV-002 Overflow before BondedLI-BL-INV-003 Move what there is, flag the restLI-BL-INV-004 Add to an open order before raising a new oneLI-BL-FUL-004 One shipment, one truckloadLI-BL-FRT-002
aws-lambdanetsuiteaws-eventbridgeaws-sesaws-secrets-manager
scheduled-lambda-run—

What each platform carries

If a platform changes, these are the rules to re-verify.

SystemRulesWhich
netsuite53 LI-BL-FUL-018 LI-BL-FUL-019 LI-BL-FUL-020 LI-BL-FUL-021 LI-BL-FUL-022 LI-BL-FUL-023 LI-BL-FUL-024 LI-BL-FUL-025 LI-BL-FUL-026 LI-BL-CMS-005 LI-BL-CMS-006 LI-BL-CMS-007 LI-BL-CMS-008 LI-BL-CMS-009 LI-BL-FUL-005 LI-BL-FUL-006 LI-BL-FUL-007 LI-BL-FUL-008 LI-BL-FUL-009 LI-BL-FUL-010 LI-BL-FUL-011 LI-BL-FUL-012 LI-BL-FUL-013 LI-BL-FUL-014 LI-BL-FUL-015 LI-BL-FUL-016 LI-BL-FUL-017 LI-BL-INV-006 LI-BL-INV-008 LI-BL-INV-009 LI-BL-INV-011 LI-BL-INV-007 LI-BL-INV-010 LI-BL-INV-012 LI-BL-INV-013 LI-BL-INV-015 LI-BL-INV-005 LI-BL-INV-014 LI-BL-ORD-001 LI-BL-FUL-001 LI-BL-FUL-002 LI-BL-FRT-001 LI-BL-FUL-003 LI-BL-CMS-001 LI-BL-CMS-002 LI-BL-CMS-003 LI-BL-CMS-004 LI-BL-INV-001 LI-BL-INV-002 LI-BL-INV-003 LI-BL-INV-004 LI-BL-FUL-004 LI-BL-FRT-002
aws-lambda37 LI-BL-FUL-018 LI-BL-FUL-019 LI-BL-FUL-020 LI-BL-FUL-021 LI-BL-FUL-022 LI-BL-FUL-023 LI-BL-FUL-024 LI-BL-FUL-025 LI-BL-FUL-026 LI-BL-CMS-005 LI-BL-CMS-006 LI-BL-CMS-007 LI-BL-CMS-008 LI-BL-CMS-009 LI-BL-FUL-005 LI-BL-FUL-006 LI-BL-FUL-007 LI-BL-FUL-008 LI-BL-FUL-009 LI-BL-FUL-010 LI-BL-FUL-011 LI-BL-FUL-012 LI-BL-FUL-013 LI-BL-FUL-014 LI-BL-FUL-015 LI-BL-FUL-016 LI-BL-FUL-017 LI-BL-FUL-001 LI-BL-FUL-002 LI-BL-FRT-001 LI-BL-FUL-003 LI-BL-INV-001 LI-BL-INV-002 LI-BL-INV-003 LI-BL-INV-004 LI-BL-FUL-004 LI-BL-FRT-002
kustomer18 LI-BL-CMS-005 LI-BL-CMS-006 LI-BL-CMS-007 LI-BL-CMS-008 LI-BL-CMS-009 LI-BL-FUL-005 LI-BL-FUL-006 LI-BL-FUL-007 LI-BL-FUL-008 LI-BL-FUL-009 LI-BL-FUL-010 LI-BL-FUL-011 LI-BL-FUL-012 LI-BL-FUL-013 LI-BL-FUL-014 LI-BL-FUL-015 LI-BL-FUL-016 LI-BL-FUL-017
google-sheets17 LI-BL-FUL-005 LI-BL-FUL-006 LI-BL-FUL-007 LI-BL-FUL-008 LI-BL-FUL-009 LI-BL-FUL-010 LI-BL-FUL-011 LI-BL-FUL-012 LI-BL-FUL-013 LI-BL-FUL-014 LI-BL-FUL-015 LI-BL-FUL-016 LI-BL-FUL-017 LI-BL-FUL-001 LI-BL-FUL-002 LI-BL-FRT-001 LI-BL-FUL-003
celigo16 LI-BL-INV-006 LI-BL-INV-008 LI-BL-INV-009 LI-BL-INV-011 LI-BL-INV-007 LI-BL-INV-010 LI-BL-INV-012 LI-BL-INV-013 LI-BL-INV-015 LI-BL-INV-005 LI-BL-INV-014 LI-BL-ORD-001 LI-BL-CMS-001 LI-BL-CMS-002 LI-BL-CMS-003 LI-BL-CMS-004
aws-eventbridge15 LI-BL-FUL-018 LI-BL-FUL-019 LI-BL-FUL-020 LI-BL-FUL-021 LI-BL-FUL-022 LI-BL-FUL-023 LI-BL-FUL-024 LI-BL-FUL-025 LI-BL-FUL-026 LI-BL-INV-001 LI-BL-INV-002 LI-BL-INV-003 LI-BL-INV-004 LI-BL-FUL-004 LI-BL-FRT-002
aws-dynamodb13 LI-BL-FUL-005 LI-BL-FUL-006 LI-BL-FUL-007 LI-BL-FUL-008 LI-BL-FUL-009 LI-BL-FUL-010 LI-BL-FUL-011 LI-BL-FUL-012 LI-BL-FUL-013 LI-BL-FUL-014 LI-BL-FUL-015 LI-BL-FUL-016 LI-BL-FUL-017
aws-end-user-messaging13 LI-BL-FUL-005 LI-BL-FUL-006 LI-BL-FUL-007 LI-BL-FUL-008 LI-BL-FUL-009 LI-BL-FUL-010 LI-BL-FUL-011 LI-BL-FUL-012 LI-BL-FUL-013 LI-BL-FUL-014 LI-BL-FUL-015 LI-BL-FUL-016 LI-BL-FUL-017
supabase13 LI-BL-FUL-005 LI-BL-FUL-006 LI-BL-FUL-007 LI-BL-FUL-008 LI-BL-FUL-009 LI-BL-FUL-010 LI-BL-FUL-011 LI-BL-FUL-012 LI-BL-FUL-013 LI-BL-FUL-014 LI-BL-FUL-015 LI-BL-FUL-016 LI-BL-FUL-017
aws-ses11 LI-BL-CMS-005 LI-BL-CMS-006 LI-BL-CMS-007 LI-BL-CMS-008 LI-BL-CMS-009 LI-BL-INV-001 LI-BL-INV-002 LI-BL-INV-003 LI-BL-INV-004 LI-BL-FUL-004 LI-BL-FRT-002
aws-cloudwatch9 LI-BL-FUL-018 LI-BL-FUL-019 LI-BL-FUL-020 LI-BL-FUL-021 LI-BL-FUL-022 LI-BL-FUL-023 LI-BL-FUL-024 LI-BL-FUL-025 LI-BL-FUL-026
shopify9 LI-BL-INV-006 LI-BL-INV-008 LI-BL-INV-009 LI-BL-INV-011 LI-BL-INV-007 LI-BL-INV-010 LI-BL-INV-012 LI-BL-INV-013 LI-BL-INV-015
aws-secrets-manager6 LI-BL-INV-001 LI-BL-INV-002 LI-BL-INV-003 LI-BL-INV-004 LI-BL-FUL-004 LI-BL-FRT-002
detrack4 LI-BL-FUL-001 LI-BL-FUL-002 LI-BL-FRT-001 LI-BL-FUL-003
aws-s34 LI-BL-FUL-001 LI-BL-FUL-002 LI-BL-FRT-001 LI-BL-FUL-003

Field ownership

Every field the documented rules touch, on which record, and which rule reads or writes it. A field written from two different entries is flagged — that is where integrations collide, and it is how several of the defects in this registry were found.

224 fields · 1 written by more than one entry

FieldRecordLabelWritten byRead by
approvalStatus Transfer Order Approval — Add to an open order before raising a new oneLI-BL-FUL-004 needs confirming
binAvailableQty Qty available from Bin — Whole bins, closest fitLI-BL-INV-002 needs confirming
binLocation Bin location — Overflow before BondedLI-BL-INV-003 needs confirming
brand Inventory Item Brand - Life Interiors — 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
brand Kit Item Brand - Life Interiors — A kit's stock is its scarcest componentLI-BL-INV-010 Whether a kit can be bought out of stockLI-BL-INV-013
commitmentfirm Transfer Order (line) Commitment Confirmed — —
consignmentNumber Item Fulfillment — Which deliveries we chaseLI-BL-FUL-018 What actually gets writtenLI-BL-FUL-024 needs confirming
current_allowBackOrder Inventory Item Shopify Enable Out Of Stock Selling — Whether an out-of-stock item can still be orderedLI-BL-INV-008
current_allowBackOrder Kit Item Shopify Enable Out Of Stock Selling — Whether a kit can be bought out of stockLI-BL-INV-013
current_bonded_receiveDate Inventory Item Next Available Receive Date (Bonded WH) — Which supply counts, and when it lands in SydneyLI-BL-INV-005
current_inStockLeadTime Inventory Item In Stock Lead Time Message — The lead-time ladder, and the words the customer readsLI-BL-INV-006
current_InStockLeadTime Kit Item In Stock Lead Time Message — A kit's promise is its slowest componentLI-BL-INV-007
current_onOrderLeadTime Inventory Item On Order Lead Time Message — The lead-time ladder, and the words the customer readsLI-BL-INV-006
current_onOrderLeadTime Kit Item On Order Lead Time Message — A kit's promise is its slowest componentLI-BL-INV-007
current_outOfStockLeadTime Inventory Item Out Of Stock Lead Time Message — The lead-time ladder, and the words the customer readsLI-BL-INV-006
current_outOfStockLeadTime Kit Item Out Of Stock Lead Time Message — A kit's promise is its slowest componentLI-BL-INV-007
current_po1_qtyAvailable Inventory Item Qty On Order Available (1st PO) — The first and second arrivalLI-BL-INV-014
current_po1_receiveDate Inventory Item Receive Date (1st PO) — The first and second arrivalLI-BL-INV-014
current_po1_stage Inventory Item PO Stage (1st PO) — The first and second arrivalLI-BL-INV-014
current_po2_qtyAvailable Inventory Item Qty On Order Available (2nd PO) — The first and second arrivalLI-BL-INV-014
current_po2_receiveDate Inventory Item Receive Date (2nd PO) — The first and second arrivalLI-BL-INV-014
current_qtyAvailable Inventory Item Qty Available To Sell On Website — The lead-time ladder, and the words the customer readsLI-BL-INV-006
current_qtyAvailable Kit Item Qty Available To Sell On Website — A kit's stock is its scarcest componentLI-BL-INV-010
current_qtyOnOrder Inventory Item Qty On Order Available To Sell On Website — The lead-time ladder, and the words the customer readsLI-BL-INV-006
current_qtyOnOrder Kit Item Qty On Order Available To Sell On Website — A kit's stock is its scarcest componentLI-BL-INV-010
current_qtySR Inventory Item — The lead-time ladder, and the words the customer readsLI-BL-INV-006 needs confirming
current_receiveDate_bonded Kit Item Next Available Receive Date (Bonded WH) — Bonded stock is netted per component, and never guessed into a Sydney dateLI-BL-INV-012
current_receiveDate Inventory Item Next Available Receive Date — The lead-time ladder, and the words the customer readsLI-BL-INV-006
current_receiveDate Kit Item Next Available Receive Date — A kit's promise is its slowest componentLI-BL-INV-007
current_shipsIn Inventory Item Ships In — The lead-time ladder, and the words the customer readsLI-BL-INV-006
current_shipsIn Kit Item Ships In — A kit's promise is its slowest componentLI-BL-INV-007
currentAllocatedPO Sales Order line Allocated PO# Finding the shipment behind the stockLI-BL-CMS-002 When we bother writing it backLI-BL-CMS-004 Finding the shipment behind the stockLI-BL-CMS-002 When we bother writing it backLI-BL-CMS-004
currentPODropShipDate Sales Order line Drop Ship Expected Ship Date When we bother writing it backLI-BL-CMS-004 When we bother writing it backLI-BL-CMS-004
custbody_actual_delivery_date Item Fulfillment What actually gets writtenLI-BL-FUL-024 — needs confirming
custbody_courier_carton_received Item Fulfillment What actually gets writtenLI-BL-FUL-024 — needs confirming
custbody_courier_tracking_comment Item Fulfillment Never overwrite something good with nothingLI-BL-FUL-022 Never move a delivery backwardsLI-BL-FUL-023 What actually gets writtenLI-BL-FUL-024 Never overwrite something good with nothingLI-BL-FUL-022 Never move a delivery backwardsLI-BL-FUL-023 What actually gets writtenLI-BL-FUL-024 needs confirming
custbody_delivery_confirmation Sales Order Customer Delivery Confirmation 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 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
custbody_delivery_status Item Fulfillment 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 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 needs confirming
custbody_detrack_truck_number Sales Order Accepting the date they choseLI-BL-FUL-013 — needs confirming
custbody_reasonforservicechange Sales Order Reason for Service Change Giving back an unconfirmed dateLI-BL-FUL-009 — needs confirming
custbody_scheduled_delivery_date_chang Sales Order — Escalating a delivery we cannot settleLI-BL-FUL-017 needs confirming
custbody_scheduled_delivery_date Sales Order Scheduled Delivery Date 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 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
custbody_scheduled_linehaul_date Sales Order Accepting the date they choseLI-BL-FUL-013 — needs confirming
custbody_to_approval Transfer Order Transfer Order Approval Add to an open order before raising a new oneLI-BL-FUL-004 —
custbody_total_cbm Transfer Order Total CBM One shipment, one truckloadLI-BL-FRT-002 One shipment, one truckloadLI-BL-FRT-002
custbody_tracking_link Item Fulfillment What actually gets writtenLI-BL-FUL-024 — needs confirming
custbody27 Sales Order Courier Approval Giving back an unconfirmed dateLI-BL-FUL-009 — needs confirming
custbodyauthority_to_leave Sales Order — One conversation per customer per dayLI-BL-FUL-006 Authority to Leave needs no replyLI-BL-FUL-008 needs confirming
custcol_agreed_due_date Sales Order line Original Lead Time Stamp the promised lead time onto the order lineLI-BL-ORD-001 —
custcol_allocated_po Sales Order line Allocated PO# Finding the shipment behind the stockLI-BL-CMS-002 When we bother writing it backLI-BL-CMS-004 —
custcol_delay_comms Sales Order line Delay Comms Recording the call, and not asking twiceLI-BL-CMS-008 —
custcol_delay_ship_date Sales Order line Delay Ship Date One request per order, every late item on itLI-BL-CMS-006 Recording the call, and not asking twiceLI-BL-CMS-008 One request per order, every late item on itLI-BL-CMS-006 Recording the call, and not asking twiceLI-BL-CMS-008
custcol_drop_ship_date Sales Order line Drop Ship Expected Ship Date When we bother writing it backLI-BL-CMS-004 —
custcolcust_item_stage Sales Order line Item Stage 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 —
custitem_celigo_shopify_enable_out_sto Inventory Item Shopify Enable Out Of Stock Selling Whether an out-of-stock item can still be orderedLI-BL-INV-008 —
custitem_celigo_shopify_enable_out_sto Kit Item Shopify Enable Out Of Stock Selling Whether a kit can be bought out of stockLI-BL-INV-013 —
custitem_next_qty_on_order_available Inventory Item Qty On Order Available (1st PO) The first and second arrivalLI-BL-INV-014 The first and second arrivalLI-BL-INV-014
custitem_next_receive_date_celigo Inventory Item On Order Lead Time Message The lead-time ladder, and the words the customer readsLI-BL-INV-006 Publishing to Shopify — product or variantLI-BL-INV-009 —
custitem_next_receive_date_celigo Kit Item On Order Lead Time Message A kit's promise is its slowest componentLI-BL-INV-007 —
custitem_out_of_stock_message Inventory Item Out Of Stock Lead Time Message The lead-time ladder, and the words the customer readsLI-BL-INV-006 Publishing to Shopify — product or variantLI-BL-INV-009 —
custitem_out_of_stock_message Kit Item Out Of Stock Lead Time Message A kit's promise is its slowest componentLI-BL-INV-007 —
custitem_po_stage Inventory Item PO Stage (1st PO) The first and second arrivalLI-BL-INV-014 The first and second arrivalLI-BL-INV-014
custitem_po2_qty_on_order_available Inventory Item Qty On Order Available (2nd PO) The first and second arrivalLI-BL-INV-014 The first and second arrivalLI-BL-INV-014
custitem_po2_receive_date Inventory Item Receive Date (2nd PO) The first and second arrivalLI-BL-INV-014 The first and second arrivalLI-BL-INV-014
custitem_qty_available_bris Inventory Item Qty Available (Bris) The lead-time ladder, and the words the customer readsLI-BL-INV-006 —
custitem_qty_available_bris Kit Item Qty Available (Bris) A kit's stock is its scarcest componentLI-BL-INV-010 —
custitem_qty_available_gc Inventory Item Qty Available (Gold Coast) The lead-time ladder, and the words the customer readsLI-BL-INV-006 —
custitem_qty_available_gc Kit Item Qty Available (Gold Coast) A kit's stock is its scarcest componentLI-BL-INV-010 —
custitem_qty_available_mel Inventory Item Qty Available (Mel) The lead-time ladder, and the words the customer readsLI-BL-INV-006 —
custitem_qty_available_mel Kit Item Qty Available (Mel) A kit's stock is its scarcest componentLI-BL-INV-010 —
custitem_qty_available_syd Inventory Item Qty Available (Syd) The lead-time ladder, and the words the customer readsLI-BL-INV-006 —
custitem_qty_available_syd Kit Item Qty Available (Syd) A kit's stock is its scarcest componentLI-BL-INV-010 —
custitem_qty_available_warehouse Inventory Item Qty Available (Warehouse) The lead-time ladder, and the words the customer readsLI-BL-INV-006 —
custitem_qty_available_warehouse Kit Item Qty Available (Warehouse) A kit's stock is its scarcest componentLI-BL-INV-010 —
custitem_qty_available_wh Inventory Item Qty Available To Sell On Website The lead-time ladder, and the words the customer readsLI-BL-INV-006 Publishing to Shopify — product or variantLI-BL-INV-009 —
custitem_qty_available_wh Kit Item Qty Available To Sell On Website A kit's stock is its scarcest componentLI-BL-INV-010 —
custitem_qty_on_order Inventory Item Qty On Order Available To Sell On Website The lead-time ladder, and the words the customer readsLI-BL-INV-006 Publishing to Shopify — product or variantLI-BL-INV-009 —
custitem_qty_on_order Kit Item Qty On Order Available To Sell On Website A kit's stock is its scarcest componentLI-BL-INV-010 —
custitem_receive_date_bonded_wh Inventory Item Next Available Receive Date (Bonded WH) Which supply counts, and when it lands in SydneyLI-BL-INV-005 Which supply counts, and when it lands in SydneyLI-BL-INV-005
custitem_ships_in_celigo Inventory Item In Stock Lead Time Message The lead-time ladder, and the words the customer readsLI-BL-INV-006 Publishing to Shopify — product or variantLI-BL-INV-009 —
custitem_ships_in_celigo Kit Item In Stock Lead Time Message A kit's promise is its slowest componentLI-BL-INV-007 —
custitem_ships_in Inventory Item Ships In The lead-time ladder, and the words the customer readsLI-BL-INV-006 —
custitem_ships_in Kit Item Ships In A kit's promise is its slowest componentLI-BL-INV-007 —
custitemcust_receive_date Inventory Item Next Available Receive Date The lead-time ladder, and the words the customer readsLI-BL-INV-006 Which supply counts, and when it lands in SydneyLI-BL-INV-005 The first and second arrivalLI-BL-INV-014 Which supply counts, and when it lands in SydneyLI-BL-INV-005 The first and second arrivalLI-BL-INV-014 two entries write this described differently
custitemcust_receive_date Kit Item Next Available Receive Date A kit's promise is its slowest componentLI-BL-INV-007 —
custom.in_stock_lead_time_message Shopify product / variant metafield Publishing to Shopify — product or variantLI-BL-INV-009 —
custom.on_order_lead_time_message Shopify product / variant metafield Publishing to Shopify — product or variantLI-BL-INV-009 —
custom.out_of_stock_lead_time_message Shopify product / variant metafield Publishing to Shopify — product or variantLI-BL-INV-009 —
custom.qty_available_wh Shopify product / variant metafield Qty Available Warehouse Publishing to Shopify — product or variantLI-BL-INV-009 —
custom.quantity_on_order Shopify product / variant metafield Publishing to Shopify — product or variantLI-BL-INV-009 —
customer_accepts_marketing Customer Customer Accepts Marketing — Which delays are handled by a callLI-BL-CMS-005
customer_address Customer Customer Address Line 1 / Line 2 / City / State / Zip — Which delays are handled by a callLI-BL-CMS-005
customer_application_approval Customer Customer Application Approval — Which delays are handled by a callLI-BL-CMS-005 needs confirming
customer_company_name Customer Customer Company Name — Which delays are handled by a callLI-BL-CMS-005
customer_fax_id Customer Customer Fax ID — Which delays are handled by a callLI-BL-CMS-005 needs confirming
customer_first_name Customer Customer First Name — Which delays are handled by a callLI-BL-CMS-005
customer_initial_contact_channel Customer Customer Initial Contact Channel — Which delays are handled by a callLI-BL-CMS-005 needs confirming
customer_internal_id Customer Customer Internal ID — Which delays are handled by a callLI-BL-CMS-005 Who the call lands withLI-BL-CMS-007
customer_last_name Customer Customer Last Name — Which delays are handled by a callLI-BL-CMS-005
customer_phone Customer Customer Phone — Which delays are handled by a callLI-BL-CMS-005
customer_shopify_store Customer Customer Shopify Store — Which delays are handled by a callLI-BL-CMS-005 needs confirming
customer_type Customer Customer Type — Who the call lands withLI-BL-CMS-007
Date Sales Order Date — Stamp the promised lead time onto the order lineLI-BL-ORD-001
days_delayed Sales Order line Days Delayed — One request per order, every late item on itLI-BL-CMS-006
email_address Customer Email Address — Which delays are handled by a callLI-BL-CMS-005
expected_ship_date Sales Order line Expected Ship Date — One request per order, every late item on itLI-BL-CMS-006 Recording the call, and not asking twiceLI-BL-CMS-008
imported Inventory Item Imported — The lead-time ladder, and the words the customer readsLI-BL-INV-006
imported Kit Item Imported — A kit's promise is its slowest componentLI-BL-INV-007
internal_id Sales Order Internal ID — Which delays are handled by a callLI-BL-CMS-005 One request per order, every late item on itLI-BL-CMS-006
internalID Inventory Item Internal ID — The lead-time ladder, and the words the customer readsLI-BL-INV-006 Which supply counts, and when it lands in SydneyLI-BL-INV-005
internalid Item Fulfillment — Which deliveries we chaseLI-BL-FUL-018 What actually gets writtenLI-BL-FUL-024 needs confirming
internalID Kit Item Internal ID — A kit's promise is its slowest componentLI-BL-INV-007 A kit's stock is its scarcest componentLI-BL-INV-010
internalID Sales Order Internal ID — Stamp the promised lead time onto the order lineLI-BL-ORD-001
item_defaultShippingMethod Inventory Item Default Shipping Method from Item record — Picking the courierLI-BL-FRT-001
item_id Item internal ID — What gets replenished, and how muchLI-BL-INV-001 needs confirming
item_packageCBM Inventory Item CBM from Item record — Picking the dayLI-BL-FUL-003
item_poStageID Inventory Item — Stamp the promised lead time onto the order lineLI-BL-ORD-001 needs confirming
item_prefferedSupplier Inventory Item Preferred Supplier — Stamp the promised lead time onto the order lineLI-BL-ORD-001
item_qtyAvailable Inventory Item Qty Available (Warehouse) — Stamp the promised lead time onto the order lineLI-BL-ORD-001
item_qtyBackordered Sales Order line — Stamp the promised lead time onto the order lineLI-BL-ORD-001 needs confirming
item_qtyCommitted Sales Order line Qty committed at SO line item — Orders that travel togetherLI-BL-FUL-002
item_qtyOnOrder Inventory Item — Stamp the promised lead time onto the order lineLI-BL-ORD-001 needs confirming
item_receiveDate Inventory Item Next Available Receive Date — Stamp the promised lead time onto the order lineLI-BL-ORD-001
item_shipDate Sales Order line Ship Date — Stamp the promised lead time onto the order lineLI-BL-ORD-001
item_shipsIn Inventory Item Ships In — Stamp the promised lead time onto the order lineLI-BL-ORD-001
item_SQOH Inventory Item Supplier Quantity On Hand — Stamp the promised lead time onto the order lineLI-BL-ORD-001
item_SQOO Inventory Item Supplier Quantity On Order — Stamp the promised lead time onto the order lineLI-BL-ORD-001
item_SRD Inventory Item Supplier Next Available Receive Date — Stamp the promised lead time onto the order lineLI-BL-ORD-001
itemallocated Qty allocated from sales order — What gets replenished, and how muchLI-BL-INV-001 Whole bins, closest fitLI-BL-INV-002 needs confirming
itemBrand Sales Order line — What the order line says on its ownLI-BL-CMS-001 What the shipment's progress saysLI-BL-CMS-003 needs confirming
itemCBM CBM from Item record — One shipment, one truckloadLI-BL-FRT-002 needs confirming
itemClosed Sales Order line Closed — What the order line says on its ownLI-BL-CMS-001
itemCurrentStage Sales Order line Item Stage 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 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
itemDelayCommsID Sales Order line Delay Comms — What the shipment's progress saysLI-BL-CMS-003
itemDropShip Sales Order line — What the order line says on its ownLI-BL-CMS-001 needs confirming
itemImported Sales Order line — What the order line says on its ownLI-BL-CMS-001 needs confirming
itemLineID Sales Order line Line ID — When we bother writing it backLI-BL-CMS-004
itemMemberName_LOOKUP Sales Order line — Finding the shipment behind the stockLI-BL-CMS-002 needs confirming
itemName Item — Finding the shipment behind the stockLI-BL-CMS-002 needs confirming
itemQtyAllocatedSupply Sales Order line — What the order line says on its ownLI-BL-CMS-001 Finding the shipment behind the stockLI-BL-CMS-002 needs confirming
itemQtyCommitted Sales Order line Quantity Committed — What the order line says on its ownLI-BL-CMS-001 Finding the shipment behind the stockLI-BL-CMS-002
itemQtyFulfilled Sales Order line Quantity Fulfilled — What the order line says on its ownLI-BL-CMS-001 What the shipment's progress saysLI-BL-CMS-003
itemQtyOrdered Sales Order line Quantity — What the order line says on its ownLI-BL-CMS-001 What the shipment's progress saysLI-BL-CMS-003
itemShipDate Sales Order line — Finding the shipment behind the stockLI-BL-CMS-002 needs confirming
itemType Item — Stamp the promised lead time onto the order lineLI-BL-ORD-001 needs confirming
kustomer_type_tree Kustomer customer — Who the call lands withLI-BL-CMS-007 needs confirming
leadSource Sales Order Lead Source — Stamp the promised lead time onto the order lineLI-BL-ORD-001
line_id Sales Order line Line ID — Recording the call, and not asking twiceLI-BL-CMS-008
lineID Sales Order line Line ID — Stamp the promised lead time onto the order lineLI-BL-ORD-001
location Transfer Order Location Overflow before BondedLI-BL-INV-003 —
member_allowBackOrder Inventory Item Shopify Enable Out Of Stock Selling — Bonded stock is netted per component, and never guessed into a Sydney dateLI-BL-INV-012 Whether a kit can be bought out of stockLI-BL-INV-013
member_inStockLeadTime Inventory Item In Stock Lead Time Message — A kit's promise is its slowest componentLI-BL-INV-007
member_onOrderLeadTime Inventory Item On Order Lead Time Message — A kit's promise is its slowest componentLI-BL-INV-007
member_outOfStockLeadTime Inventory Item Out Of Stock Lead Time Message — A kit's promise is its slowest componentLI-BL-INV-007
member_receiveDate_bonded Inventory Item Next Available Receive Date (Bonded WH) — Bonded stock is netted per component, and never guessed into a Sydney dateLI-BL-INV-012
member_receiveDate Inventory Item Next Available Receive Date — A kit's promise is its slowest componentLI-BL-INV-007
member_shipsIn Inventory Item Ships In — A kit's promise is its slowest componentLI-BL-INV-007
memberID Inventory Item — A kit's promise is its slowest componentLI-BL-INV-007 needs confirming
memberName Inventory Item — A kit's promise is its slowest componentLI-BL-INV-007 needs confirming
name1 Customer Name1 — Which delays are handled by a callLI-BL-CMS-005 needs confirming
new_receiveDate_bonded Inventory Item Next Available Receive Date (Bonded WH) — Bonded stock on hand, and paying off the backorder firstLI-BL-INV-011
new_receiveDate_bonded Kit Item — Bonded stock is netted per component, and never guessed into a Sydney dateLI-BL-INV-012
new_receiveDate Inventory Item Next Available Receive Date — 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
newPODropShipDate Sales Order line — When we bother writing it backLI-BL-CMS-004 needs confirming
OLD OLT Sales Order line Original Lead Time — Stamp the promised lead time onto the order lineLI-BL-ORD-001
order_number Sales Order Order Number — One request per order, every late item on itLI-BL-CMS-006
original_lead_time Sales Order line Original Lead Time — One request per order, every late item on itLI-BL-CMS-006
overrideleadtimedays Transfer Order Override Lead Time (Days) Overflow before BondedLI-BL-INV-003 —
POExpectedReceiveDate Purchase Order — Finding the shipment behind the stockLI-BL-CMS-002 needs confirming
poInternalID Transaction Internal ID — Which supply counts, and when it lands in SydneyLI-BL-INV-005
PONumber Purchase Order Document Number — Finding the shipment behind the stockLI-BL-CMS-002 When we bother writing it backLI-BL-CMS-004
poNumber Transaction Document Number — Which supply counts, and when it lands in SydneyLI-BL-INV-005
POQtyAllocatedDemand Purchase Order — Finding the shipment behind the stockLI-BL-CMS-002 needs confirming
POQtyOrdered Purchase Order Quantity — Finding the shipment behind the stockLI-BL-CMS-002
poReceiveDate Transaction Line Expected Receipt Date — Which supply counts, and when it lands in SydneyLI-BL-INV-005
POStage Purchase Order Purchase Order Stage — What the shipment's progress saysLI-BL-CMS-003 needs confirming
poStage Transaction PO Stage — The first and second arrivalLI-BL-INV-014 needs confirming
POStageID Purchase Order — What the shipment's progress saysLI-BL-CMS-003 needs confirming
product Sales Order line Product — One request per order, every late item on itLI-BL-CMS-006
productName Inventory Item Display Name — Which supply counts, and when it lands in SydneyLI-BL-INV-005
qtyAllocatedDemand Transaction Line — Which supply counts, and when it lands in SydneyLI-BL-INV-005
qtyAvailable_bonded Inventory Item Qty Available (Bonded Warehouse) — 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
qtyAvailable_bris Inventory Item Qty Available (Bris) The lead-time ladder, and the words the customer readsLI-BL-INV-006 The lead-time ladder, and the words the customer readsLI-BL-INV-006 A kit's stock is its scarcest componentLI-BL-INV-010
qtyAvailable_gc Inventory Item Qty Available (Gold Coast) The lead-time ladder, and the words the customer readsLI-BL-INV-006 The lead-time ladder, and the words the customer readsLI-BL-INV-006 A kit's stock is its scarcest componentLI-BL-INV-010
qtyAvailable_mel Inventory Item Qty Available (Mel) The lead-time ladder, and the words the customer readsLI-BL-INV-006 The lead-time ladder, and the words the customer readsLI-BL-INV-006 A kit's stock is its scarcest componentLI-BL-INV-010
qtyAvailable_syd Inventory Item Qty Available (Syd) The lead-time ladder, and the words the customer readsLI-BL-INV-006 The lead-time ladder, and the words the customer readsLI-BL-INV-006 A kit's stock is its scarcest componentLI-BL-INV-010
qtyAvailable_warehouse Inventory Item Qty Available (Warehouse) — The lead-time ladder, and the words the customer readsLI-BL-INV-006 A kit's stock is its scarcest componentLI-BL-INV-010
qtyAvailable_warehouse2 Inventory Item — 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 A kit's stock is its scarcest componentLI-BL-INV-010 Whether a kit can be bought out of stockLI-BL-INV-013 needs confirming
QtyDemand Qty demand from sales order — What gets replenished, and how muchLI-BL-INV-001 needs confirming
qtyOnOrder_bonded Inventory Item — 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 needs confirming
qtyOnOrder_warehouse Inventory Item — 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 A kit's promise is its slowest componentLI-BL-INV-007 A kit's stock is its scarcest componentLI-BL-INV-010 needs confirming
qtyRemaining Transaction Line — Which supply counts, and when it lands in SydneyLI-BL-INV-005
shipdate Sales Order Ship Date Giving back an unconfirmed dateLI-BL-FUL-009 Accepting the date they choseLI-BL-FUL-013 —
shipmethod Item Fulfillment Ship Via — Which deliveries we chaseLI-BL-FUL-018 Matching a delivery to its carrierLI-BL-FUL-019 needs confirming
shopifyItemType Inventory Item — Publishing to Shopify — product or variantLI-BL-INV-009
shopifyItemType Kit Item — A kit's promise is its slowest componentLI-BL-INV-007
shopifyProductID Inventory Item — Publishing to Shopify — product or variantLI-BL-INV-009
shopifyProductID Kit Item — A kit's promise is its slowest componentLI-BL-INV-007
shopifyVariantID Inventory Item — Publishing to Shopify — product or variantLI-BL-INV-009
shopifyVariantID Kit Item — A kit's promise is its slowest componentLI-BL-INV-007
SO_courierServiceLevel Sales Order Courier Service Level — Picking the courierLI-BL-FRT-001
SO_cxRequestedDate Sales Order Customer Requested Delivery Date Onwards — Picking the dayLI-BL-FUL-003
SO_lifeRegion Sales Order Life Truck Region — Picking the dayLI-BL-FUL-003
SO_postcode Sales Order Shipping Postcode — Picking the courierLI-BL-FRT-001
SO_shipTogetherWithID Sales Order Ship Together With This Sales Order — Orders that travel togetherLI-BL-FUL-002
SO_shipVia Sales Order Ship Via Picking the courierLI-BL-FRT-001 Picking the courierLI-BL-FRT-001
SO_state Sales Order Shipping State — Picking the dayLI-BL-FUL-003
SOInternalID Sales Order Internal ID — When we bother writing it backLI-BL-CMS-004
SOnumber Sales Order Document Number — Stamp the promised lead time onto the order lineLI-BL-ORD-001
SONumber Sales Order Document Number — —
supplier_defaultInStockLeadTime Inventory Item Default In Stock Lead Time — The lead-time ladder, and the words the customer readsLI-BL-INV-006
supplier_defaultMadeToOrderLeadTime1 Inventory Item Default Made To Order 1 Lead Time — The lead-time ladder, and the words the customer readsLI-BL-INV-006 A kit's promise is its slowest componentLI-BL-INV-007
supplier_defaultMadeToOrderLeadTime2 Inventory Item Default Made To Order 2 Lead Time — The lead-time ladder, and the words the customer readsLI-BL-INV-006 A kit's promise is its slowest componentLI-BL-INV-007
supplier_defaultOutOfStockLeadTime Inventory Item Default Out Of Stock Lead Time — The lead-time ladder, and the words the customer readsLI-BL-INV-006
supplier_isDropShip Inventory Item Drop Ship — The lead-time ladder, and the words the customer readsLI-BL-INV-006
supplier_qtyAvailable Inventory Item Supplier Quantity On Hand — 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 Publishing to Shopify — product or variantLI-BL-INV-009 A kit's stock is its scarcest componentLI-BL-INV-010 Whether a kit can be bought out of stockLI-BL-INV-013
supplier_qtyOnOrder Inventory Item Supplier Quantity On Order — 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 Publishing to Shopify — product or variantLI-BL-INV-009 A kit's stock is its scarcest componentLI-BL-INV-010 Whether a kit can be bought out of stockLI-BL-INV-013
supplier_receiveDate Inventory Item Supplier Next Available Receive Date — 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
supplyType Inventory Item Supply Type — 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
supplyType Kit Item Supply Type — Whether a kit can be bought out of stockLI-BL-INV-013
toLocationID Transaction Line — Which supply counts, and when it lands in SydneyLI-BL-INV-005
trandate Transfer Order Date — —
tranid Item Fulfillment — Which deliveries we chaseLI-BL-FUL-018 needs confirming
transferlocation Transfer Order To Location Add to an open order before raising a new oneLI-BL-FUL-004 —

Known gaps — not documented yet

The maps above draw only what the registry contains. These are known to exist and are not in it. Absence from the maps is not evidence of absence in the business.

WhatSystemNote
Lead Time flow 4 — the Celigo calculation
celigo
The entry exists and the NetSuite side is verified, but the script that decides the date has not been read. Entry is draft.
Celigo integration "NetSuite Scripts" — the other flow groupings
celigo
Roughly seventy live flows across Landed Cost, ODIN, Supply Chain, Pricing, Shopify Refunds and others. Only two are documented — Original Lead Time V2 and Supply Chain - Item Stage Update V3.
Item Purchase Order Stage (parts 1 and 2)
celigo
Maintains the PO stage that the Original Lead Time search reads, and that LI-BL-CMS-003 buckets into the wording customers see. Feeds two documented rules but is not itself documented.
Saved searches 4085 and 4084 — the Item Stage feeds
netsuite
LI-BL-CMS-001 to 004 are documented from the Celigo scripts, but the criteria of the two searches feeding them have not been read. A line outside search 4085 keeps its message forever with no error anywhere, and the sort order of search 4084 silently decides which purchase order wins when more than one is acceptable.
Supply chain and delay notification emails
aws
The main consumer of LI-BL-ORD-001, and of the Item Stage message written by LI-BL-CMS-003. What it sends, and when, is undocumented. The Celigo flow that writes back to the sales order after those emails ("Supply Chain - Update SO after Emails sent by AWS") is undocumented too. It was recorded here as the likeliest place the Delay Comms field is set; that now holds only for Stage 1. The Stage 2 value is written by the kustomer-delay-comms Lambda, verified against production and documented at LI-BL-CMS-008 — so what remains unknown is who sets Stage 1.
Delay Comms Stage 1 — the message the customer actually receives
aws
The first contact when an item slips, and the thing LI-BL-CMS-005 to 009 assume has already happened. NetSuite carries two live script searches for it — customsearch5152 (SMS) and customsearch6155 (Klaviyo) — plus an inactive Dotdigital one, and the wording sits in templates outside version control. Whether both fire, which is authoritative, and what either says are all unread, so nothing in the registry can state what a customer was told. Stage 2 contacts nobody, so this is the only customer-facing half of delay comms and it is the undocumented one.
Delay Comms Stage 2 — the eligibility saved search (N_SEARCHID)
netsuite
The search that decides which lines get a call. It is held in the Lambda's environment, not in the repository, so LI-BL-CMS-005 documents what the automation does with the lines it is given and not which lines those are — the days-delayed threshold, the overseas restriction the search names imply, and the drop-ship exclusion the code's own comment expects are all unread. The only Stage 2 script search in NetSuite is customsearch3826, and it is marked *legacy despite the automation being live.
Delay Comms Stage 2 — the deployment (schedule and invocation)
aws
Nothing in the kustomer-delay-comms repository declares a trigger, and there is no CI workflow. The once-daily run at about 13:30 Sydney time in LI-BL-CMS-005 was read off the creation times of the conversations the automation raises, not off a schedule, so it is documented but unverified — and a run started by hand is indistinguishable from a scheduled one except by its timestamp, which is how defect DN-D6 was found.
NS-Queuer — the saved search extractor and user note RESTlets
netsuite
Two RESTlets that kustomer-delay-comms calls by script id through the NS-Queuer API Gateway, neither of which lives in the repository that calls them. The extractor's response shape is what LI-BL-CMS-005 parses (a JSON string with a header row to discard); the user note RESTlet's per-entry result contract is what LI-BL-CMS-009 checks to decide whether the audit log was really written. Neither can be verified from git, and both are shared with other integrations.
Shipping Automation module 2 — set ship date
celigo
The downstream of the no-confirmation reset in LI-BL-FUL-009. A released delivery falls back into it for a new ship date, which restarts the confirmation conversation. Not documented.
Availability engine — ms-courier-schedule-loader-v2
aws
Reads the "WH PICKING SCHEDULE - INTEGRATION SCHEDULE" Google Sheet and NetSuite CBM limits. Feeds courier-schedule-sync. Not documented.
Availability engine — courier-schedule-sync into Supabase
aws
Upserts runs, run availability and run capacity into the lifeinte-fulfillment Supabase database every ~10 minutes. The dates offered to customers in LI-BL-FUL-012 come from here, so stale data here means offering dates that have no capacity. Not documented.
lifeinte-fulfillment API
aws
The API the inbound delivery-confirmation Lambda calls for available dates. Reads the Supabase tables above. Not documented.
lifedeldateconfirm-s13-reminder deployment
aws
The reminder Lambda has no CI workflow and no recorded workflow run, so what is deployed cannot be confirmed from GitHub. LI-BL-FUL-016 documents the code, not a verified deployment.
Courier tracking — the NetSuite RESTlet (LI_courier_status_update_rl.js)
netsuite
The script the courier tracking Lambda reads saved search 7756 through and writes the five delivery fields back through. It holds the field whitelist that decides what can be written at all. It lives in NetSuite; the courier-tracking-status repository references it but does not track it, so nothing about it can be verified from git.
Courier tracking — saved search 7756
netsuite
The only definition of which deliveries get tracked. LI-BL-FUL-018 describes how the automation treats the rows it receives, not what puts them there. Whether supplier-account ship methods are already excluded from it is unconfirmed.
Courier tracking — the deployment (schedule, alarm, packaging)
aws
The EventBridge rule, the SNS alert topic and the CloudWatch alarm are described in the repository README but are not in version control — template.yaml, build.sh, SETUP.md, canary.mjs and local-run.mjs are all referenced there and none is tracked. The twice-daily schedule in LI-BL-FUL-018 is therefore documented but unverified.
ap-tracking-status-update — the Lambda courier tracking replaces
aws
The courier tracking README describes a cutover that leaves the old AusPost-only Lambda running alongside the new one for about a week. Whether it completed is unestablished, so it is not known whether two automations are writing the same delivery fields.
Shopify storefront rendering
shopify
Four metafields are written by the lead-time chain. How the theme displays them is undocumented.