Fulfillment Examination Findings and Product Questions
Findings distinguish observed defects, conflicting evidence, undocumented behavior and delivery debt. Product questions reserve decisions that determine the planning boundary or authority. Source locators are retained in frontmatter.
Findings
| Id | Severity | Statement | Affects | Kind |
|---|---|---|---|---|
FND-COM-FUL-001 | high | The delivery-coordination and physical-goods milestones remain proposed, while the realignment document proposes new milestone numbering. Implementation and section walkthroughs do not establish Product acceptance for the module; capability intent remains proposed except where the staff-order decision supplies authority. | MOD-COM-FUL, OQ-COM-FUL-001 | inconsistency |
FND-COM-FUL-002 | medium | The staff-order plan still labels itself proposed even though the milestone index records approval and the milestone record says Andrew requested the recommended options. Its header conflicts with those authority records. | CAP-COM-FUL-002, CAP-COM-FUL-003, BR-CAP-COM-FUL-002-06 | inconsistency |
FND-COM-FUL-003 | medium | The Commerce acceptance seed inventory belongs to another console branch and is absent from the pinned commit. Its historical identifiers support supersession tracing but do not provide pinned executable proof. | MOD-COM-FUL | undocumented |
FND-COM-FUL-004 | high | The pinned console lacks the complete policy, shipping-configuration, warehouse, picking, packing, handover, receiving and stock-management workflows. Service operations establish those capabilities, while the available order cards provide only limited entry points. | CAP-COM-FUL-001, CAP-COM-FUL-010, CAP-COM-FUL-012, CAP-COM-FUL-013, CAP-COM-FUL-014, CAP-COM-FUL-015, CAP-COM-FUL-016, CAP-COM-FUL-017, CAP-COM-FUL-019, BR-CAP-COM-FUL-016-08 | debt |
FND-COM-FUL-005 | medium | Order 360 requests a label without manual tracking or cost details and offers no packing workflow. Its manual-carrier path therefore cannot complete ordinary label preparation from that card alone. | CAP-COM-FUL-012, CAP-COM-FUL-013, BR-CAP-COM-FUL-012-12 | inconsistency |
FND-COM-FUL-006 | medium | The acknowledgement dialog describes application receipt of an authorization, but the service records staff awareness of an exception. The screen explanation misstates the action's effect. | CAP-COM-FUL-008, BR-CAP-COM-FUL-008-03 | inconsistency |
FND-COM-FUL-007 | medium | Several displayed interventions lack service routes or an appropriate subject route. Choosing these unavailable actions cannot perform tender retry, mirror reconciliation, label void, return receipt or reservation release. | CAP-COM-FUL-008, BR-CAP-COM-FUL-008-08 | debt |
FND-COM-FUL-008 | high | Inventory retains stock and shipping problems in its own findings list, which Operations does not read. Operations also groups several declared kinds that no scoped producer raises, leaving warehouse problems outside the visible queue. | CAP-COM-FUL-008, CAP-COM-FUL-012, CAP-COM-FUL-013, CAP-COM-FUL-019, OQ-COM-FUL-004 | inconsistency |
FND-COM-FUL-009 | medium | The reconciler continues to skip scheduled amendments, overdue returns and inventory balances as later-phase work. Inventory now performs a separate nightly balance check, but the declared operations checks remain placeholders. | CAP-COM-FUL-009, BR-CAP-COM-FUL-009-10 | debt |
FND-COM-FUL-010 | high | The selected Platform audit provider logs intervention events instead of storing them in Platform because its writer is absent. Commerce's append-only intervention ledger remains the durable attribution record, and the declared Platform action list covers only part of Commerce's catalogue. | CAP-COM-FUL-005, CAP-COM-FUL-008, BR-CAP-COM-FUL-005-09 | undocumented |
FND-COM-FUL-011 | medium | The financial position provider supplies no approved-customer-terms fact. The console billed-on-terms rule supplies a separate approval path, leaving the general customer-terms policy setting without that Accounting evidence. | CAP-COM-FUL-002, BR-CAP-COM-FUL-002-13, BR-CAP-COM-FUL-002-06 | inconsistency |
FND-COM-FUL-012 | low | Some migration and policy comments retain the older order-type terminology even though their implementation now uses ordering profiles. These comments need alignment with the current selection model. | CAP-COM-FUL-001, CAP-COM-FUL-020 | inconsistency |
FND-COM-FUL-013 | low | Policy application is an explicit bounded service intervention rather than a tracked data job. It provides no job-level progress record for large scopes, and continuation limitations are recorded separately. | CAP-COM-FUL-001, BR-CAP-COM-FUL-001-08 | debt |
FND-COM-FUL-014 | medium | Terminate and allocation-release operations remain in the delivery vocabulary, but the worker acknowledges them with a warning instead of invoking an application. No scoped document currently produces those instructions. | CAP-COM-FUL-004, BR-CAP-COM-FUL-004-13 | undocumented |
FND-COM-FUL-015 | low | The obligation dead-letter queue has no consumer or implemented redrive workflow. Reconciliation measures its depth and does not turn that measurement into an operational finding. | CAP-COM-FUL-004, CAP-COM-FUL-009 | debt |
FND-COM-FUL-016 | medium | Carrier tracking runs only on request. Scheduled tracking, carrier notifications, stored label files, Accounting posting of carrier cost and returned-to-sender receiving are not established by the scoped implementation. | CAP-COM-FUL-013, CAP-COM-FUL-015, BR-CAP-COM-FUL-013-12 | debt |
FND-COM-FUL-017 | medium | The shipping record reports that a live UPS call was not tested and that the deployed platform transport was unconfigured. Local gateway and scripted-carrier tests establish fixture behavior without establishing live carrier operation. | CAP-COM-FUL-011, CAP-COM-FUL-013 | undocumented |
FND-COM-FUL-018 | medium | Return disposition rejects replacement while replacement obligations are unavailable. Exchanges therefore remain outside the supported physical return outcome. | CAP-COM-FUL-015, BR-CAP-COM-FUL-015-07 | debt |
FND-COM-FUL-019 | medium | Purchasing and cost records are registered with Orders even though stock transfer, shipment departure, return disposition and inventory reconciliation invoke cost behavior. Product needs to settle the ownership boundary before design divides these coupled operations. | CAP-COM-FUL-014, CAP-COM-FUL-017, CAP-COM-FUL-019, OQ-COM-FUL-002 | inconsistency |
FND-COM-FUL-020 | low | Ten declared permissions have no requiring route: the bulk permissions for policies, zones, strategies, accounts, shipments, pick lists and return receipts, plus deletion of shipments, pick lists and return receipts. Permission declaration does not establish an available operation. | MOD-COM-FUL | debt |
FND-COM-FUL-021 | low | The register's stale-work and acknowledgement passes run through the Orders checkout sweep. Scheduling responsibility and specification ownership therefore cross the registered module boundary. | CAP-COM-FUL-002, CAP-COM-FUL-004 | inconsistency |
FND-COM-FUL-022 | medium | Policy resolution does not use the contract's tender-requirement default selection. An ordering profile without its own configured policy falls back to workspace or built-in full-payment behavior instead. | CAP-COM-FUL-001 | undocumented |
FND-COM-FUL-023 | low | The operations module declares the idempotency ledger used across Commerce. Its physical placement does not establish exclusive operations ownership of request replay. | CAP-COM-FUL-008 | debt |
FND-COM-FUL-024 | low | Operations loads no more than 1,000 findings into a view and then searches and sorts that collection locally. Service responses do not expose the total or perform those search and sorting choices. | CAP-COM-FUL-008, BR-CAP-COM-FUL-008-10 | debt |
FND-COM-FUL-025 | medium | Order 360 exposes recovery, resolution, hold release and override, while approval, hold placement and manual completion remain service-only. Staff cannot assume every intervention exists on the delivery card. | CAP-COM-FUL-005, BR-CAP-COM-FUL-005-10 | inconsistency |
FND-COM-FUL-026 | low | The module registry now names the Operations components, adapters and authorization files reached from its owned page. The corrected scope distinguishes that page from Order 360, whose delivery and shipment cards are hosted evidence. | MOD-COM-FUL | undocumented |
FND-COM-FUL-027 | low | No pinned browser test proves the complete module journeys. Service end-to-end tests and console library tests provide partial evidence, and the required browser acceptance scenario remains proposed. | JNY-COM-FUL-001, JNY-COM-FUL-002, JNY-COM-FUL-003, JNY-COM-FUL-004 | debt |
FND-COM-FUL-028 | medium | The data-job workflow loads collections owned by several Commerce modules under their collection authorities. Only warehouse, location and stock records are clearly within this module's physical-stock ownership, leaving import ownership for Product to settle. | CAP-COM-FUL-020, OQ-COM-FUL-003 | undocumented |
FND-COM-FUL-029 | medium | The console intervention rule, shipment-permission rule and in-flight manual-label resolution rule retain unbound proposed acceptance work. Existing tests do not establish all their stated outcomes, and fractional rounding and the complete browser workflow add further proposed proof. | CAP-COM-FUL-005, CAP-COM-FUL-012, CAP-COM-FUL-013 | debt |
FND-COM-FUL-030 | medium | The requested authoring brief is absent from the starting documentation commit. Examination cannot establish additional scope or decisions from that missing input. | MOD-COM-FUL | undocumented |
FND-COM-FUL-031 | high | Stale-obligation recovery reads bounded pages and excludes blocked dependents, so it does not guarantee recovery within ten minutes or recover every failed prerequisite settlement. Policy application repeatedly reads its first pending page without a cursor, allowing unchanged entries to obstruct examination of later entries. | CAP-COM-FUL-001, CAP-COM-FUL-002, CAP-COM-FUL-003 | defect |
FND-COM-FUL-032 | high | The draft conflates some metrics, fixtures and workflow outcomes with stronger evidence. Direct checks show no dead-letter exception, earlier blocked-billing findings and a reversal backstop without cancellation-document inspection; deferred cost fixtures and library tests also do not prove actual costing or complete browser behavior. | CAP-COM-FUL-009, CAP-COM-FUL-014, JNY-COM-FUL-001, JNY-COM-FUL-002 | inconsistency |
FND-COM-FUL-033 | medium | Percentage eligibility rounds upward in code, while the cited unit examples have integral thresholds. The proposed fractional-boundary scenario needs a new executable test before its proof can be relied on. | BR-CAP-COM-FUL-002-14, ATS-COM-FUL-002-10 | debt |
FND-COM-FUL-034 | high | After authorization, a physical unit's delivery waits in progress under a 24-hour acknowledgement deadline. The register sweep re-sends it once and fails it as acknowledgement lost at the next deadline. Goods still in the warehouse after about two days (a backorder, a slow second wave) therefore fail delivery, and the handoff refuses them until staff re-authorize. Inferred from the code; no test drives a unit past two deadlines. | WF-COM-FUL-003, WF-COM-FUL-012, STATE-COM-FUL-001, CAP-COM-FUL-004, CAP-COM-FUL-012, OQ-COM-FUL-005 | defect |
FND-COM-FUL-035 | medium | Receiving and disposition commit the warehouse's rows and then run the return document's money step. If that step fails, nothing retries it: a repeated receipt returns the recorded one, a repeated disposition is refused, and the reconciler's returns check is skipped. A dispositioned return can be left without its credit memo or refund, and no finding is raised. | WF-COM-FUL-014, CAP-COM-FUL-015, BR-CAP-COM-FUL-015-08 | defect |
FND-COM-FUL-036 | medium | The Create Shipment dialog asks for per-line quantities, a carrier, the ship-to, a ship date, tracking, a weight and whether to e-mail the customer. Its request carries only the chosen lines and the notes. The service ships every committed unit of each chosen line from one warehouse with the order's own carrier and address, and the other values are dropped without saying so. | SCR-COM-FUL-004, CAP-COM-FUL-012 | inconsistency |
FND-COM-FUL-037 | medium | Only the obligation lifecycle is guarded by the database. Shipment, shipment line, parcel, pick list, return receipt, allocation, count and finding states are checked by the workflows and by conditional updates. A write outside those workflows could move them in ways their state models forbid. | STATE-COM-FUL-005, STATE-COM-FUL-006, STATE-COM-FUL-007, STATE-COM-FUL-008, STATE-COM-FUL-009, STATE-COM-FUL-010 | debt |
FND-COM-FUL-038 | medium | The intervention ledger and the operational exceptions are declared by the fulfillment module but are also written by Orders (a void, cancellation, amendment and return approvals, entitlement grants, a staff-applied promotion) and by the operations module. No contract names who may write them or which vocabulary each writer owns. | DOM-COM-FUL-001, DOM-COM-FUL-003, ADR-COM-FUL-001, OQ-COM-FUL-006 | undocumented |
FND-COM-FUL-039 | low | The module asks no model a question, so it has no inference directory. The conventions require the module charter to say so in one sentence, and the approved charter does not; adding it is a planning correction. | MOD-COM-FUL | undocumented |
FND-COM-FUL-040 | medium | The architecture package and the Platform standards the code follows live in a repository this draft could not read. The design names the standard each mechanism follows from the code's own references (queued work, jobs, persistence, indexing, row-level security, time), and the verification pass should confirm them against the standards themselves. | ADR-COM-FUL-003, ADR-COM-FUL-004, ADR-COM-FUL-005, ADR-COM-FUL-013, ADR-COM-FUL-020 | undocumented |
FND-COM-FUL-041 | low | The intervention dialog says Release Hold "releases the held stock or seats so they can be sold again". On an obligation the action releases a staff hold on delivery and moves no stock. | SCR-COM-FUL-001, SCR-COM-FUL-002, CAP-COM-FUL-005 | inconsistency |
FND-COM-FUL-042 | low | No module of this area publishes change events. Other applications learn about delivery through the calls they receive, Platform's record history sees none of these records, and the register's history is kept in Commerce's own append-only logs and the order's history. | SVC-COM-FUL-fulfillment, SVC-COM-FUL-shipping, SVC-COM-FUL-inventory, ADR-COM-FUL-022 | debt |
FND-COM-FUL-043 | low | A carrier's live rate at checkout is asked from the workspace's first active warehouse, with the whole weight as one parcel. The shipment may later leave from another warehouse in several parcels, so the charge a buyer pays and the carrier's cost can differ. | WF-COM-FUL-010, CAP-COM-FUL-011 | undocumented |
FND-COM-FUL-044 | low | The draft inferred the four health operation names from another module. Examination of the installed shared route factory confirms those names and public access; this evidence gap is closed. | SVC-COM-FUL-fulfillment, SVC-COM-FUL-shipping, SVC-COM-FUL-inventory, SVC-COM-FUL-operations | undocumented |
| FND-COM-FUL-045 | medium | The parcel model invents a label-requested parcel state. Purchase intent belongs to the carrier-label attempt, while the parcel remains packed until purchase succeeds. | STATE-COM-FUL-006, WF-COM-FUL-011 | inconsistency | | FND-COM-FUL-046 | high | Delivery outcomes commit before some history, exception and enforcement writes. Failure afterwards can leave a terminal obligation without those records, and queue redelivery treats it as stale. Re-authorizing a failed enforce obligation also leaves its enforcement failed, where a completed outcome cannot settle it. | WF-COM-FUL-003, STATE-COM-FUL-002 | defect | | FND-COM-FUL-047 | high | Handoff rejects matching obligations outside the in-flight states but does not compare their count or unit indexes with every allocation being shipped. Missing obligation rows can therefore escape that check; the design must not promise complete authorization coverage from this function alone. | DOM-COM-FUL-004, WF-COM-FUL-012, BR-CAP-COM-FUL-014-02 | defect | | FND-COM-FUL-048 | medium | Complete-payload validation is a proposed design extension. Shipping replacement schemas require identity, version and active status but retain optional properties, so the draft incorrectly describes every incomplete replacement as refused. | ADR-COM-FUL-019, SVC-COM-FUL-shipping | inconsistency | | FND-COM-FUL-049 | medium | Several draft workflows promise recovery within ten minutes or continuation on repeated policy application. The planning layer already limits recovery to bounded pending scans and records policy application rereading its first page; the design now reflects those limits. | WF-COM-FUL-001, WF-COM-FUL-002, WF-COM-FUL-004, WF-COM-FUL-008 | inconsistency | | FND-COM-FUL-050 | medium | The dispatch decision claimed confirmed authority from a Platform standard that neither draft nor examiner can inspect in the available repositories. Code establishes the mechanism, so its design intent is proposed pending an accessible authority record. | ADR-COM-FUL-004, FND-COM-FUL-040 | undocumented | | FND-COM-FUL-051 | high | Pick-list creation checks for existing open-list membership before insertion. Database uniqueness applies within each list, so concurrent creations can include the same shipment line on different live lists; the draft exclusion guarantee is stronger than the implementation. | WF-COM-FUL-010, STATE-COM-FUL-007, BR-CAP-COM-FUL-012-04 | defect | | FND-COM-FUL-052 | high | Enforcement creation commits before dispatch or staff-review creation. Event redelivery skips an enforcement that already exists, so a failure between those writes can strand a pending enforcement without its instruction or review finding. | WF-COM-FUL-005, SVC-COM-FUL-fulfillment | defect |
| FND-COM-FUL-053 | medium | Delivery and operations interventions retain local records, but their selected shared audit provider only logs the event; it supplies no durable publication to the shared audit store. | CAP-COM-FUL-001, CAP-COM-FUL-005, CAP-COM-FUL-006, CAP-COM-FUL-007, CAP-COM-FUL-008, WF-COM-FUL-008, WF-COM-FUL-009, SVC-COM-FUL-fulfillment, SVC-COM-FUL-operations | control-gap | | FND-COM-FUL-054 | high | A delivery outcome can commit before its history and follow-up writes; repeated callbacks skip the applied outcome and do not reconstruct all omitted records, leaving durable work without complete recovery. | CAP-COM-FUL-004, WF-COM-FUL-003, SVC-COM-FUL-fulfillment | control-gap | | FND-COM-FUL-055 | high | Pick-list creation checks existing live-list membership before insertion without excluding another concurrent creation; the same shipment line can enter two active lists without a conflict. | CAP-COM-FUL-012, WF-COM-FUL-010, SVC-COM-FUL-shipping | control-gap |
Open Questions
| Id | Question | Why It Matters | Options | Recommendation | Affects |
|---|---|---|---|---|---|
OQ-COM-FUL-001 | Which section verdicts or milestone decisions should confirm this module's delivery and warehouse rules? | Design needs a reliable distinction between observed implementation and approved product behavior. | Confirm section verdict coverage; approve the owning milestone plans; or decide rule-by-rule in a module walkthrough. | The product should record rule-level decisions in a walkthrough and carry them into the owning plans. | MOD-COM-FUL |
OQ-COM-FUL-002 | Where should purchasing and inventory costing be owned in the specification? | Physical stock operations and monetary relief interact within the same transaction boundaries. | Move them into fulfillment; retain Orders ownership with an explicit contract; or establish a separate purchasing and costing module. | The product should group purchasing and costing with stock unless a deliberate separate boundary is approved. | CAP-COM-FUL-014, CAP-COM-FUL-017, CAP-COM-FUL-019 |
OQ-COM-FUL-003 | Should each migration import belong to the module owning the loaded collection? | A shared data-job workflow currently spans several record owners and risks duplicating product facts. | Keep all imports here; assign collection-specific behavior to its owner; or establish a Commerce migration module. | The product should specify each import with its record owner and retain Platform ownership of the shared engine. | CAP-COM-FUL-020 |
OQ-COM-FUL-004 | How should staff discover warehouse and carrier findings alongside order problems? | The current Operations collection does not include inventory findings. | Read both finding lists in one queue; build a warehouse queue; or keep warehouse investigation service-only. | The product should provide a shared attention workflow with a warehouse filter. | CAP-COM-FUL-008, CAP-COM-FUL-019 |
OQ-COM-FUL-005 | How long may a physical unit wait in the warehouse before its delivery is treated as lost? | Today a backordered or slow unit fails its delivery after about two days, and staff must re-authorize it before the goods can leave. | Keep the deadline and the staff re-authorization; let the merchandise application renew the deadline while the unit is waiting in the warehouse; or exempt physical units from the acknowledgement deadline and rely on warehouse findings. | The product should exempt physical units that are still on the shelf from the acknowledgement deadline and raise a warehouse finding for an overdue shipment instead. | CAP-COM-FUL-004, CAP-COM-FUL-012, FND-COM-FUL-034 |
OQ-COM-FUL-006 | Which module owns the intervention ledger and the operational exceptions that several Commerce modules write? | One ledger serves every staff intervention in Commerce. Until its owner and its writers are named, a change made for one module can break another's history. | Keep both in Fulfillment and name every writer in its contract; move them to an Operations module that owns the queue and the reconciler; or give each module its own ledger and read them together. | The product should keep them in Fulfillment and record each writing module and its intervention kinds in the service contract. | DOM-COM-FUL-001, DOM-COM-FUL-003, FND-COM-FUL-038 |
OQ-COM-FUL-007 | Should the policy, shipping configuration, warehouse, picking, packing, receiving and stock screens be specified now, before any exists in the console? | The design layer can describe only the screens that exist. Warehouse and administrator journeys run through service operations alone. | Specify them now from the service contracts; wait for a ticket that builds each; or keep them service-only. | The product should specify them when a ticket builds them, from the service contracts, with v0 for the new screens. | CAP-COM-FUL-001, CAP-COM-FUL-010, CAP-COM-FUL-012, CAP-COM-FUL-015, CAP-COM-FUL-016, CAP-COM-FUL-019, FND-COM-FUL-004 |