Fulfillment Planning Examination
Scope and Method
The examination reads the authoring contract, planning templates and the four approved broad CRM concepts before reviewing the Commerce draft. The requested planning brief is absent from the starting documentation commit; the missing input remains a finding. Source repositories remain at their supplied commits, and this job makes no source-code, deployment or workflow changes. The job instruction to commit on the supplied branch governs this ephemeral checkout instead of the ordinary worktree landing process.
Source inspection covers registered routes, schemas, persistence, database declarations, background resources, console adapters, cited tests and product records. Locator checks open the cited files at their pinned commits and check ordinary test titles and symbols; composite finding references and annotated intent locators are reviewed as record references. Test binding establishes evidence in a source test, not a claim that that service test ran during this documentation job. The required executable checks exercise the documentation corpus.
Counts Examined
| Item | Count |
|---|---|
| Existing module files | 59 |
| Module charters / ledgers / findings files | 1 / 1 / 1 |
| Features / concepts / capabilities / journeys / acceptance sets | 5 / 5 / 20 / 6 / 20 |
| Commerce actor rows | 6 |
| Initial rule rows / final rule rows | 219 / 220 |
| Final must-prove rules | 188 |
| Final acceptance scenarios | 135 |
| Final journey steps / assertions | 37 / 18 |
| Existing findings / new findings / product questions | 29 / 4 / 4 |
All existing planning prose and structured customer-facing text is rewritten. Each capability and acceptance set has its own final-text commit following the verification commits; concepts, features and journeys also have individual commits. Names used as stable product nouns, source locators, identifiers and permission keys remain technical labels rather than new claims. No artifact advances to approved status.
Coverage
Coverage below means a named capability or evidence home exists. It does not mean Product approval or executable proof of every variant.
| Surface | Covered / Total | Home | Uncovered by Name |
|---|---|---|---|
| Resolved business HTTP operations | 104 / 104 | Operation map below | None; 89 literal declarations plus 15 shipping-configuration factory instances |
| Data-job operations | 132 / 132 | CAP-COM-FUL-020 | None; eleven operations for each of twelve collections |
| Public health-route instances | 4 / 4 | Route evidence; CAP-COM-FUL-008 covers operations health | None in route indexing; health endpoints are infrastructure evidence |
| Table declaration files | 34 / 34 | Table map below | None; the data-job file expands shared-engine tables |
| Declared permission keys in scoped groups | 60 / 60 | Permission map below | Ten unused declarations remain FND-COM-FUL-020 |
| Service test files | 83 / 83 | Test evidence map below | None in indexing; not all tests are acceptance bindings |
| Service end-to-end files | 13 / 13 | Included in test map | None in indexing |
| Primary queues and their dead-letter queues | 2 / 2 primary, 2 / 2 dead-letter | CAP-COM-FUL-004 and CAP-COM-FUL-020 | Obligation redrive workflow remains absent |
| Schedules declared in scoped modules | 4 / 4 | Dispatcher, reconciler, data-job dispatcher, inventory nightly | None; checkout-owned register passes are an external scheduling dependency |
| State machines | 0 / 0 | No declaration in scoped resources | None |
| Owned console pages | 1 / 1 | Operations; CAP-COM-FUL-008 | Complete warehouse and configuration screens remain absent |
| Hosted Order 360 cards | 2 / 2 | CAP-COM-FUL-005 and CAP-COM-FUL-012 | Full intervention and warehouse progression remain incomplete |
| Required rules with a scenario | 188 / 188 | Acceptance sets | None without a proposed or bound scenario |
| Required rules with at least one existing binding | 184 / 188 | Acceptance sets | BR-CAP-COM-FUL-002-14, BR-CAP-COM-FUL-005-10, BR-CAP-COM-FUL-012-11, BR-CAP-COM-FUL-013-03 |
| Complete browser journeys | 0 / 4 required | FND-COM-FUL-027; ATS-COM-FUL-008-06 is proposed | JNY-COM-FUL-001, JNY-COM-FUL-002, JNY-COM-FUL-003, JNY-COM-FUL-004 |
Verification Changes
| Artifact or Row | Correction and Evidence |
|---|---|
| BR-CAP-COM-FUL-002-12; SC-CAP-COM-FUL-002-03; JNY-COM-FUL-001 alternate | Replace ten-minute recovery guarantee with stale eligibility and bounded paging. The register sweep reads limited pending candidates. |
| BR-CAP-COM-FUL-002-14; ATS-COM-FUL-002-10 | Add upward rounding of percentage thresholds and an unbound fractional-boundary unit scenario. |
| BR-CAP-COM-FUL-003-08 | Replace nonexistent settleDependentsOf locator with settlePrerequisiteDependents and remove guaranteed sweep recovery for blocked dependents. |
| BR-CAP-COM-FUL-005-09 | Describe selected audit invocation and the Platform provider's logging limitation rather than claim successful Platform storage. |
| BR-CAP-COM-FUL-008-06 | Distinguish kind-based permission menu logic from subject-based service-route availability. |
| ATS-COM-FUL-008-06 | Remove partial bindings, use proposed provenance and browser level, and cite the missing-browser finding. |
| BR-CAP-COM-FUL-009-02 | Blocked billing candidates already older than ten minutes raise an exception; sixty minutes applies to other unbilled candidates. |
| BR-CAP-COM-FUL-009-05 | State that the reversal backstop does not inspect cancellation documents. |
| BR-CAP-COM-FUL-009-06 | Replace claimed dead-letter finding with metric-only behavior. |
| BR-CAP-COM-FUL-014-10; SC-CAP-COM-FUL-014-01; JNY-COM-FUL-003 cost assertion | Describe the selected cost seam and deferred fixture facts without inferring actual layered or zero-cost relief from the seam. |
| BR-CAP-COM-FUL-016-08 | Replace unsupported permission-file proof of absent pages with unknown provenance and the screen-gap finding. |
| BR-CAP-COM-FUL-017-09 | Include missing reason and inactive destination refusals observed in transfer service. |
| SC-CAP-COM-FUL-017-01; ATS-COM-FUL-017-04 | Match the receipt fixture: three received, two committed and one available. |
| CON-COM-FUL-001 relationships; CON-COM-FUL-003 obligation relationship | Narrow composite and numerical generalizations to the outcomes demonstrated by their cited tests. |
| CON-COM-FUL-004 lifecycle | Remove a universal terminal-state claim not established by the cited declaration. |
| JNY-COM-FUL-005 unsupported restoration; JNY-COM-FUL-006 missing dependency alternate | Retain staff work and dependency waiting without claiming that the cited test proves later completion. |
| MODULE.md | Replace the embedded coverage catalogue with this examination inventory, correct literal-versus-factory operation counting and retain unresolved ownership boundaries. |
| ID_REGISTRY.md; FINDINGS.md | Reserve the new rounding and examination ids before authoring; record four new findings and rewrite all questions as explicit product decisions. |
| MOD-COM-FUL registry row | Change only its planning state to planning examined. |
For route-level permission claims, provenance names the observed owning route; broader state, worker and library claims retain their matching test or console evidence. These are the exact affected rows:
- BR-CAP-COM-FUL-001-10 → services-commerce:modules/fulfillment/aws/api/fulfillment.routes.ts
- BR-CAP-COM-FUL-004-08 → services-commerce:modules/fulfillment/aws/api/fulfillment.routes.ts
- BR-CAP-COM-FUL-005-08 → services-commerce:modules/fulfillment/aws/api/fulfillment.routes.ts
- BR-CAP-COM-FUL-006-11 → services-commerce:modules/operations/aws/api/operations.routes.ts
- BR-CAP-COM-FUL-008-04 → services-commerce:modules/operations/aws/api/operations.routes.ts
- BR-CAP-COM-FUL-010-09 → services-commerce:modules/shipping/aws/api/shipping.routes.ts
- BR-CAP-COM-FUL-014-09 → services-commerce:modules/shipping/aws/api/shipping.routes.ts
- BR-CAP-COM-FUL-015-11 → services-commerce:modules/shipping/aws/api/shipping.routes.ts
- BR-CAP-COM-FUL-017-12 → services-commerce:modules/inventory/aws/api/inventory.routes.ts
- BR-CAP-COM-FUL-019-12 → services-commerce:modules/inventory/aws/api/inventory.routes.ts
Additional locator verification corrects FND-COM-FUL-001, FND-COM-FUL-002, FND-COM-FUL-003, FND-COM-FUL-005, FND-COM-FUL-007, FND-COM-FUL-010, FND-COM-FUL-011, FND-COM-FUL-012, FND-COM-FUL-015, FND-COM-FUL-016, FND-COM-FUL-017, FND-COM-FUL-022, FND-COM-FUL-029. A read-only fetch confirms all 88 supersession capability identifiers in the acceptance seed inventory at its separate recorded commit; that inventory is not a proof binding at the pinned console commit. All five concepts gain observed provenance and pinned sources on every facet. Console permission source corrections also cover BR-CAP-COM-FUL-008-06 and BR-CAP-COM-FUL-008-09, while enforcement reads use the operations route for BR-CAP-COM-FUL-006-11.
Final-Text Artifact Index
| Artifact | Final Text |
|---|---|
| MOD-COM-FUL | Fulfillment, Shipping and Inventory |
| ATS-COM-FUL-001 | undefined |
| ATS-COM-FUL-002 | undefined |
| ATS-COM-FUL-003 | undefined |
| ATS-COM-FUL-004 | undefined |
| ATS-COM-FUL-005 | undefined |
| ATS-COM-FUL-006 | undefined |
| ATS-COM-FUL-007 | undefined |
| ATS-COM-FUL-008 | undefined |
| ATS-COM-FUL-009 | undefined |
| ATS-COM-FUL-010 | undefined |
| ATS-COM-FUL-011 | undefined |
| ATS-COM-FUL-012 | undefined |
| ATS-COM-FUL-013 | undefined |
| ATS-COM-FUL-014 | undefined |
| ATS-COM-FUL-015 | undefined |
| ATS-COM-FUL-016 | undefined |
| ATS-COM-FUL-017 | undefined |
| ATS-COM-FUL-018 | undefined |
| ATS-COM-FUL-019 | undefined |
| ATS-COM-FUL-020 | undefined |
| CAP-COM-FUL-001 | Choose delivery conditions for sold items |
| CAP-COM-FUL-002 | Authorize delivery from current order facts |
| CAP-COM-FUL-003 | Protect a member-priced purchase until its membership arrives |
| CAP-COM-FUL-004 | Carry authorized work to its delivering application |
| CAP-COM-FUL-005 | Understand and intervene in an order's delivery |
| CAP-COM-FUL-006 | Handle financial reversals after delivery |
| CAP-COM-FUL-007 | Complete the financial work requested by a post-sale document |
| CAP-COM-FUL-008 | Review and resolve operations findings |
| CAP-COM-FUL-009 | Detect stalled and inconsistent order work |
| CAP-COM-FUL-010 | Configure shipping coverage and collection options |
| CAP-COM-FUL-011 | Quote shipping and pickup choices for a cart |
| CAP-COM-FUL-012 | Prepare an order's goods for dispatch |
| CAP-COM-FUL-013 | Purchase and follow carrier labels safely |
| CAP-COM-FUL-014 | Record goods leaving with a carrier or collector |
| CAP-COM-FUL-015 | Process returned goods through inspection and disposition |
| CAP-COM-FUL-016 | Organize warehouses and stock locations |
| CAP-COM-FUL-017 | Keep stock movements and transfers accountable |
| CAP-COM-FUL-018 | Allocate stock and explain what buyers can obtain |
| CAP-COM-FUL-019 | Reconcile shelf counts and stock findings |
| CAP-COM-FUL-020 | Import Commerce history and reconcile source records |
| CON-COM-FUL-001 | Obligation |
| CON-COM-FUL-002 | Fulfilment Policy |
| CON-COM-FUL-003 | Operational Exception |
| CON-COM-FUL-004 | Shipment |
| CON-COM-FUL-005 | Stock |
| FEAT-COM-FUL-01 | Delivery Conditions and Coordination |
| FEAT-COM-FUL-02 | Order Problems and Financial Follow-Up |
| FEAT-COM-FUL-03 | Physical Delivery and Returns |
| FEAT-COM-FUL-04 | Stock Records and Reconciliation |
| FEAT-COM-FUL-05 | Historical Commerce Imports |
| JNY-COM-FUL-001 | Staff follow a paid order through application delivery |
| JNY-COM-FUL-002 | Operations staff recover and close a failed delivery |
| JNY-COM-FUL-003 | Warehouse staff dispatch an order in successive waves |
| JNY-COM-FUL-004 | Warehouse staff return goods to stock and complete the refund |
| JNY-COM-FUL-005 | Staff follow reversal enforcement and restored funds |
| JNY-COM-FUL-006 | Implementation staff load and reconcile Commerce history |
| ACT-COM-008 through ACT-COM-013 | Commerce staff and service actor descriptions, goals and broad actions |
| ID_REGISTRY.md | Identifier purpose and allocation labels |
| FINDINGS.md | Every finding statement and product-question field |
Open Disagreements
Every retained finding remains open for the stated evidence and Product disposition; this examination does not close a finding by rewriting it.
| Finding | Remaining Issue |
|---|---|
| FND-COM-FUL-001 | 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. |
| FND-COM-FUL-002 | 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. |
| FND-COM-FUL-003 | 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. |
| FND-COM-FUL-004 | 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. |
| FND-COM-FUL-005 | 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. |
| FND-COM-FUL-006 | 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. |
| FND-COM-FUL-007 | 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. |
| FND-COM-FUL-008 | 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. |
| FND-COM-FUL-009 | 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. |
| FND-COM-FUL-010 | 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. |
| FND-COM-FUL-011 | 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. |
| FND-COM-FUL-012 | 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. |
| FND-COM-FUL-013 | 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. |
| FND-COM-FUL-014 | 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. |
| FND-COM-FUL-015 | 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. |
| FND-COM-FUL-016 | 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. |
| FND-COM-FUL-017 | 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. |
| FND-COM-FUL-018 | Return disposition rejects replacement while replacement obligations are unavailable. Exchanges therefore remain outside the supported physical return outcome. |
| FND-COM-FUL-019 | 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. |
| FND-COM-FUL-020 | 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. |
| FND-COM-FUL-021 | 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. |
| FND-COM-FUL-022 | 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. |
| FND-COM-FUL-023 | The operations module declares the idempotency ledger used across Commerce. Its physical placement does not establish exclusive operations ownership of request replay. |
| FND-COM-FUL-024 | 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. |
| FND-COM-FUL-025 | 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. |
| FND-COM-FUL-026 | 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. |
| FND-COM-FUL-027 | 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. |
| FND-COM-FUL-028 | 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. |
| FND-COM-FUL-029 | 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. |
| FND-COM-FUL-030 | The requested authoring brief is absent from the starting documentation commit. Examination cannot establish additional scope or decisions from that missing input. |
| FND-COM-FUL-031 | 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. |
| FND-COM-FUL-032 | 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. |
| FND-COM-FUL-033 | 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. |
The four material Product decisions remain OQ-COM-FUL-001 through OQ-COM-FUL-004: approval authority, costing ownership, import ownership and the warehouse attention surface.
Validation
The starting corpus and each committed rewrite pass npm run check with zero errors. Final acceptance passes npm ci && npm run check with zero conformance errors and npm test with four tests passed and zero failures. No service database preparation is needed because no service integration or end-to-end suite is executed by this documentation job.
Verdict for Andrew
The layer describes the pinned module with sourced corrections and explicit findings where the evidence does not establish a stronger claim. Its weakest areas are product authority, complete browser proof, live carrier evidence and bounded recovery behavior. Before design starts, settle the four Product questions and assign the recovery, warehouse-surface and proposed-proof gaps to approved work.
Operation Evidence Map
| Operation | Capability |
|---|---|
| listObligations | CAP-COM-FUL-005 |
| getObligation | CAP-COM-FUL-005 |
| completeObligation | CAP-COM-FUL-004 |
| failObligation | CAP-COM-FUL-004 |
| reportObligationPrerequisite | CAP-COM-FUL-004 |
| approveObligation | CAP-COM-FUL-005 |
| overrideObligationGate | CAP-COM-FUL-005 |
| reauthorizeObligation | CAP-COM-FUL-005 |
| resolveObligation | CAP-COM-FUL-005 |
| holdObligation | CAP-COM-FUL-005 |
| releaseObligationHold | CAP-COM-FUL-005 |
| completeObligationManually | CAP-COM-FUL-005 |
| createFulfillmentPolicy | CAP-COM-FUL-001 |
| listFulfillmentPolicies | CAP-COM-FUL-001 |
| getEffectiveFulfillmentPolicy | CAP-COM-FUL-001 |
| getFulfillmentPolicy | CAP-COM-FUL-001 |
| updateFulfillmentPolicy | CAP-COM-FUL-001 |
| deleteFulfillmentPolicy | CAP-COM-FUL-001 |
| applyFulfillmentPolicy | CAP-COM-FUL-001 |
| createWarehouse | CAP-COM-FUL-016 |
| listWarehouses | CAP-COM-FUL-016 |
| getWarehouse | CAP-COM-FUL-016 |
| updateWarehouse | CAP-COM-FUL-016 |
| deleteWarehouse | CAP-COM-FUL-016 |
| createInventoryLocation | CAP-COM-FUL-016 |
| listInventoryLocations | CAP-COM-FUL-016 |
| getInventoryLocation | CAP-COM-FUL-016 |
| updateInventoryLocation | CAP-COM-FUL-016 |
| deleteInventoryLocation | CAP-COM-FUL-016 |
| listInventoryItems | CAP-COM-FUL-017 |
| readSkuAvailability | CAP-COM-FUL-018 |
| getInventoryItem | CAP-COM-FUL-017 |
| updateInventoryItemSettings | CAP-COM-FUL-017 |
| recordInventoryMovement | CAP-COM-FUL-017 |
| listInventoryMovements | CAP-COM-FUL-017 |
| getInventoryMovement | CAP-COM-FUL-017 |
| transferInventory | CAP-COM-FUL-017 |
| listInventoryTransfers | CAP-COM-FUL-017 |
| listInventoryAllocations | CAP-COM-FUL-018 |
| getInventoryAllocation | CAP-COM-FUL-018 |
| openInventoryCount | CAP-COM-FUL-019 |
| listInventoryCounts | CAP-COM-FUL-019 |
| getInventoryCount | CAP-COM-FUL-019 |
| recordInventoryCountLines | CAP-COM-FUL-019 |
| completeInventoryCount | CAP-COM-FUL-019 |
| cancelInventoryCount | CAP-COM-FUL-019 |
| listInventoryExceptions | CAP-COM-FUL-019 |
| getInventoryException | CAP-COM-FUL-019 |
| acknowledgeInventoryException | CAP-COM-FUL-019 |
| resolveInventoryException | CAP-COM-FUL-019 |
| listOperationalExceptions | CAP-COM-FUL-008 |
| summarizeOperationalExceptions | CAP-COM-FUL-008 |
| getOperationalException | CAP-COM-FUL-008 |
| acknowledgeOperationalException | CAP-COM-FUL-008 |
| resolveOperationalException | CAP-COM-FUL-008 |
| listFinancialAdjustments | CAP-COM-FUL-007 |
| getFinancialAdjustment | CAP-COM-FUL-007 |
| retryFinancialAdjustment | CAP-COM-FUL-007 |
| resolveFinancialAdjustment | CAP-COM-FUL-007 |
| listEnforcements | CAP-COM-FUL-006 |
| getEnforcement | CAP-COM-FUL-006 |
| resolveEnforcement | CAP-COM-FUL-006 |
| createShipment | CAP-COM-FUL-012 |
| listShipments | CAP-COM-FUL-012 |
| getShipment | CAP-COM-FUL-012 |
| listShipmentEvents | CAP-COM-FUL-012 |
| listShipmentPackages | CAP-COM-FUL-012 |
| releaseShipment | CAP-COM-FUL-012 |
| packShipment | CAP-COM-FUL-012 |
| purchasePackageLabel | CAP-COM-FUL-013 |
| resolvePackageLabel | CAP-COM-FUL-013 |
| voidPackageLabel | CAP-COM-FUL-013 |
| trackPackage | CAP-COM-FUL-013 |
| manifestShipment | CAP-COM-FUL-012 |
| handoffShipment | CAP-COM-FUL-014 |
| handoverShipment | CAP-COM-FUL-014 |
| cancelShipment | CAP-COM-FUL-012 |
| createPickList | CAP-COM-FUL-012 |
| listPickLists | CAP-COM-FUL-012 |
| getPickList | CAP-COM-FUL-012 |
| claimPickList | CAP-COM-FUL-012 |
| pickPickListLine | CAP-COM-FUL-012 |
| completePickList | CAP-COM-FUL-012 |
| cancelPickList | CAP-COM-FUL-012 |
| receiveReturn | CAP-COM-FUL-015 |
| listReturnReceipts | CAP-COM-FUL-015 |
| getReturnReceipt | CAP-COM-FUL-015 |
| inspectReturnReceipt | CAP-COM-FUL-015 |
| dispositionReturnReceipt | CAP-COM-FUL-015 |
| createShippingZone | CAP-COM-FUL-010 |
| listShippingZones | CAP-COM-FUL-010 |
| getShippingZone | CAP-COM-FUL-010 |
| updateShippingZone | CAP-COM-FUL-010 |
| deleteShippingZone | CAP-COM-FUL-010 |
| createShippingStrategy | CAP-COM-FUL-010 |
| listShippingStrategies | CAP-COM-FUL-010 |
| getShippingStrategy | CAP-COM-FUL-010 |
| updateShippingStrategy | CAP-COM-FUL-010 |
| deleteShippingStrategy | CAP-COM-FUL-010 |
| createCarrierAccount | CAP-COM-FUL-010 |
| listCarrierAccounts | CAP-COM-FUL-010 |
| getCarrierAccount | CAP-COM-FUL-010 |
| updateCarrierAccount | CAP-COM-FUL-010 |
| deleteCarrierAccount | CAP-COM-FUL-010 |
Tables By Capability
| Table file | Capabilities |
|---|---|
fulfillment/db/obligations.table.ts | CAP-COM-FUL-004, CAP-COM-FUL-005 |
fulfillment/db/obligation-authorizations.table.ts | CAP-COM-FUL-004 |
fulfillment/db/obligation-attempts.table.ts | CAP-COM-FUL-004 |
fulfillment/db/obligation-dispatches.table.ts | CAP-COM-FUL-004 |
fulfillment/db/fulfillment-policies.table.ts | CAP-COM-FUL-001 |
fulfillment/db/enforcements.table.ts | CAP-COM-FUL-006 |
fulfillment/db/financial-adjustments.table.ts | CAP-COM-FUL-007 |
fulfillment/db/financial-fact-receipts.table.ts | CAP-COM-FUL-002 |
fulfillment/db/intervention-logs.table.ts | CAP-COM-FUL-005, CAP-COM-FUL-008 |
fulfillment/db/operational-exceptions.table.ts | CAP-COM-FUL-008, CAP-COM-FUL-009 |
shipping/db/shipping-zones.table.ts | CAP-COM-FUL-010 |
shipping/db/shipping-strategies.table.ts | CAP-COM-FUL-010 |
shipping/db/carrier-accounts.table.ts | CAP-COM-FUL-010 |
shipping/db/shipments.table.ts | CAP-COM-FUL-012, CAP-COM-FUL-014 |
shipping/db/shipment-lines.table.ts | CAP-COM-FUL-012, CAP-COM-FUL-014 |
shipping/db/packages.table.ts | CAP-COM-FUL-012 |
shipping/db/package-lines.table.ts | CAP-COM-FUL-012 |
shipping/db/pick-lists.table.ts | CAP-COM-FUL-012 |
shipping/db/pick-list-lines.table.ts | CAP-COM-FUL-012 |
shipping/db/shipment-events.table.ts | CAP-COM-FUL-012 |
shipping/db/carrier-labels.table.ts | CAP-COM-FUL-013 |
shipping/db/return-receipts.table.ts | CAP-COM-FUL-015 |
shipping/db/return-receipt-lines.table.ts | CAP-COM-FUL-015 |
shipping/db/return-dispositions.table.ts | CAP-COM-FUL-015 |
inventory/db/warehouses.table.ts | CAP-COM-FUL-016 |
inventory/db/inventory-locations.table.ts | CAP-COM-FUL-016 |
inventory/db/inventory-items.table.ts | CAP-COM-FUL-017 |
inventory/db/inventory-movements.table.ts | CAP-COM-FUL-017 |
inventory/db/inventory-allocations.table.ts | CAP-COM-FUL-018 |
inventory/db/inventory-counts.table.ts | CAP-COM-FUL-019 |
inventory/db/inventory-count-lines.table.ts | CAP-COM-FUL-019 |
inventory/db/inventory-exceptions.table.ts | CAP-COM-FUL-019 |
operations/db/idempotency-keys.table.ts | CAP-COM-FUL-008 (FND-COM-FUL-023) |
data-operations/db/data-jobs.table.ts | CAP-COM-FUL-020 (the Data Job Engine’s eight tables) |
Permission Keys
| Permission key | Capability or evidence home |
|---|---|
commerce.obligations.read | CAP-COM-FUL-005, CAP-COM-FUL-003 |
commerce.obligations.approve | CAP-COM-FUL-005 |
commerce.obligations.override | CAP-COM-FUL-005 |
commerce.obligations.reauthorize | CAP-COM-FUL-005 |
commerce.obligations.resolve | CAP-COM-FUL-005 |
commerce.obligations.hold | CAP-COM-FUL-005 |
commerce.obligations.complete-manually | CAP-COM-FUL-005 |
commerce.obligations.callback | CAP-COM-FUL-004 |
commerce.fulfillment-policies.read | CAP-COM-FUL-001 |
commerce.fulfillment-policies.create | CAP-COM-FUL-001 |
commerce.fulfillment-policies.update | CAP-COM-FUL-001 |
commerce.fulfillment-policies.delete | CAP-COM-FUL-001 |
commerce.fulfillment-policies.apply | CAP-COM-FUL-001 |
commerce.fulfillment-policies.bulk | FND-COM-FUL-020 (required by no route) |
commerce.exceptions.read | CAP-COM-FUL-008 |
commerce.exceptions.acknowledge | CAP-COM-FUL-008 |
commerce.exceptions.resolve | CAP-COM-FUL-008 |
commerce.adjustments.read | CAP-COM-FUL-007 |
commerce.adjustments.retry | CAP-COM-FUL-007 |
commerce.adjustments.resolve | CAP-COM-FUL-007 |
commerce.enforcements.read | CAP-COM-FUL-006 |
commerce.enforcements.resolve | CAP-COM-FUL-006 |
commerce.shipping-zones.read | CAP-COM-FUL-010 |
commerce.shipping-zones.create | CAP-COM-FUL-010 |
commerce.shipping-zones.update | CAP-COM-FUL-010 |
commerce.shipping-zones.delete | CAP-COM-FUL-010 |
commerce.shipping-zones.bulk | FND-COM-FUL-020 (required by no route) |
commerce.shipping-strategies.read | CAP-COM-FUL-010 |
commerce.shipping-strategies.create | CAP-COM-FUL-010 |
commerce.shipping-strategies.update | CAP-COM-FUL-010 |
commerce.shipping-strategies.delete | CAP-COM-FUL-010 |
commerce.shipping-strategies.bulk | FND-COM-FUL-020 (required by no route) |
commerce.carrier-accounts.read | CAP-COM-FUL-010 |
commerce.carrier-accounts.create | CAP-COM-FUL-010 |
commerce.carrier-accounts.update | CAP-COM-FUL-010 |
commerce.carrier-accounts.delete | CAP-COM-FUL-010 |
commerce.carrier-accounts.bulk | FND-COM-FUL-020 (required by no route) |
commerce.shipments.read | CAP-COM-FUL-012 |
commerce.shipments.create | CAP-COM-FUL-012 |
commerce.shipments.update | CAP-COM-FUL-012, CAP-COM-FUL-013 |
commerce.shipments.handoff | CAP-COM-FUL-014 |
commerce.shipments.handover | CAP-COM-FUL-014 |
commerce.shipments.cancel | CAP-COM-FUL-012 |
commerce.shipments.delete | FND-COM-FUL-020 (required by no route) |
commerce.shipments.bulk | FND-COM-FUL-020 (required by no route) |
commerce.pick-lists.read | CAP-COM-FUL-012 |
commerce.pick-lists.create | CAP-COM-FUL-012 |
commerce.pick-lists.update | CAP-COM-FUL-012 |
commerce.pick-lists.delete | FND-COM-FUL-020 (required by no route) |
commerce.pick-lists.bulk | FND-COM-FUL-020 (required by no route) |
commerce.return-receipts.read | CAP-COM-FUL-015 |
commerce.return-receipts.create | CAP-COM-FUL-015 |
commerce.return-receipts.update | CAP-COM-FUL-015 |
commerce.return-receipts.delete | FND-COM-FUL-020 (required by no route) |
commerce.return-receipts.bulk | FND-COM-FUL-020 (required by no route) |
commerce.inventory.read | CAP-COM-FUL-016 to 019 |
commerce.inventory.create | CAP-COM-FUL-016, 017, 019 |
commerce.inventory.update | CAP-COM-FUL-016, 017, 019, 020 |
commerce.inventory.delete | CAP-COM-FUL-016 |
commerce.inventory.bulk | CAP-COM-FUL-020 |
Test Files By Capability
| Test file | Capabilities (CAP-COM-FUL-) |
|---|---|
fulfillment/tests/e2e/enforcement.e2e.spec.js | 006 |
fulfillment/tests/e2e/fulfillment-paid-amount.e2e.spec.js | 001, 002 |
fulfillment/tests/e2e/fulfillment-policies.e2e.spec.js | 001 |
fulfillment/tests/e2e/obligation-holds.e2e.spec.js | 005 |
fulfillment/tests/e2e/obligation-register.e2e.spec.js | 002, 004, 005 |
fulfillment/tests/e2e/same-cart-grants.e2e.spec.js | 003 |
fulfillment/tests/integration/db/obligations.table.integration.spec.js | 004 |
fulfillment/tests/integration/db/register-tables.table.integration.spec.js | 001, 004, 005, 006, 007, 008 |
fulfillment/tests/integration/services/adjustments/adjustment-worker.integration.spec.js | 007 |
fulfillment/tests/integration/services/enforcement/enforcement-handler.integration.spec.js | 006 |
fulfillment/tests/integration/services/facts/financial-facts-handler.integration.spec.js | 002, 007 |
fulfillment/tests/integration/services/facts/position-view-gate.integration.spec.js | 002 |
fulfillment/tests/integration/services/persistence/enforcements.queries.integration.spec.js | 006 |
fulfillment/tests/integration/services/persistence/financial-adjustments.queries.integration.spec.js | 007 |
fulfillment/tests/integration/services/persistence/financial-fact-receipts.queries.integration.spec.js | 002 |
fulfillment/tests/integration/services/persistence/fulfillment-policies.integration.spec.js | 001 |
fulfillment/tests/integration/services/persistence/fulfillment-policies.queries.integration.spec.js | 001 |
fulfillment/tests/integration/services/persistence/intervention-logs.queries.integration.spec.js | 005 |
fulfillment/tests/integration/services/persistence/obligation-attempts.queries.integration.spec.js | 004 |
fulfillment/tests/integration/services/persistence/obligation-authorizations.queries.integration.spec.js | 004 |
fulfillment/tests/integration/services/persistence/obligation-dispatches.queries.integration.spec.js | 004 |
fulfillment/tests/integration/services/persistence/obligation-holds.integration.spec.js | 005 |
fulfillment/tests/integration/services/persistence/obligation-register.integration.spec.js | 002, 004, 005, 008 |
fulfillment/tests/integration/services/persistence/obligations.integration.spec.js | 004 |
fulfillment/tests/integration/services/persistence/obligations.queries.integration.spec.js | 003, 004, 005 |
fulfillment/tests/integration/services/persistence/operational-exceptions.queries.integration.spec.js | 008 |
fulfillment/tests/integration/services/register/obligation-dispatcher.integration.spec.js | 004 |
fulfillment/tests/integration/services/register/obligation-worker.integration.spec.js | 004 |
fulfillment/tests/integration/services/register/prerequisite-settlement.integration.spec.js | 003 |
fulfillment/tests/integration/services/register/register-sweeper.integration.spec.js | 002, 004 |
fulfillment/tests/unit/adjustments/accounting-adjustment-commands.spec.js | 007 |
fulfillment/tests/unit/adjustments/adjustment-pending-at-processor.spec.js | 007 |
fulfillment/tests/unit/adjustments/adjustment-planning.spec.js | 007 |
fulfillment/tests/unit/facts/change-events-contract.spec.js | 002 |
fulfillment/tests/unit/policies/evaluate-gate.spec.js | 002 |
fulfillment/tests/unit/policies/policy-resolution.spec.js | 001 |
fulfillment/tests/unit/register/obligation-approval.spec.js | 005 |
fulfillment/tests/unit/register/obligation-queue.spec.js | 004 |
fulfillment/tests/unit/register/order-billed-on-terms.spec.js | 002 |
shipping/tests/e2e/post-purchase-shipping.e2e.spec.js | 014, 015 |
shipping/tests/e2e/shipping.e2e.spec.js | 010, 011, 012, 013, 014 |
shipping/tests/integration/db/return-receiving-tables.table.integration.spec.js | 015 |
shipping/tests/integration/db/shipping-tables.table.integration.spec.js | 010, 012, 013, 014 |
shipping/tests/integration/services/fulfillment/shipping-flow.integration.spec.js | 012, 013, 014 |
shipping/tests/integration/services/persistence/return-receipts.queries.integration.spec.js | 015 |
shipping/tests/integration/services/persistence/shipment-events.queries.integration.spec.js | 012 |
shipping/tests/integration/services/persistence/shipping-configuration.integration.spec.js | 010, 011 |
shipping/tests/integration/services/returns/return-receiving.integration.spec.js | 015 |
shipping/tests/unit/api/blank-shipping-configuration-values.spec.js | 010, 011 |
shipping/tests/unit/carriers/carrier-adapters.spec.js | 011, 013 |
shipping/tests/unit/rating/zone-strategy-rating.spec.js | 011 |
inventory/tests/e2e/inventory.e2e.spec.js | 016, 017, 018, 019 |
inventory/tests/e2e/merchandise-placement.e2e.spec.js | 017, 018 |
inventory/tests/integration/db/inventory-tables.table.integration.spec.js | 016, 017, 018, 019 |
inventory/tests/integration/services/persistence/inventory-configuration.integration.spec.js | 016 |
inventory/tests/integration/services/persistence/inventory-transfers.queries.integration.spec.js | 017 |
inventory/tests/integration/services/reconciliation/nightly-inventory-paging.integration.spec.js | 019 |
inventory/tests/integration/services/reconciliation/nightly-inventory.integration.spec.js | 019 |
inventory/tests/integration/services/stock/inventory-transfers.integration.spec.js | 017 |
inventory/tests/integration/services/stock/merchandise-claims.integration.spec.js | 018 |
inventory/tests/integration/services/stock/staff-movements.integration.spec.js | 017, 019 |
inventory/tests/unit/stock/staff-movement-keys.spec.js | 017 |
operations/tests/e2e/health.e2e.spec.js | 008 |
operations/tests/e2e/operations.e2e.spec.js | 007, 008 |
operations/tests/integration/services/interventions/operations-interventions.integration.spec.js | 006, 007, 008 |
operations/tests/integration/services/persistence/reconciler-candidates.queries.integration.spec.js | 009 |
operations/tests/integration/services/reconciler/reconciler.integration.spec.js | 009 |
operations/tests/unit/reconciler/reconciler-catalogue.spec.js | 009 |
data-operations/tests/e2e/data-jobs.e2e.spec.js | 020 |
data-operations/tests/integration/services/jobs/data-jobs.integration.spec.js | 020 |
data-operations/tests/integration/services/operations/catalog-import.integration.spec.js | 020 |
data-operations/tests/integration/services/operations/configuration-imports.integration.spec.js | 020 |
data-operations/tests/integration/services/operations/inventory-import.integration.spec.js | 020 |
data-operations/tests/integration/services/operations/merchandise-import.integration.spec.js | 020 |
data-operations/tests/integration/services/operations/order-import.integration.spec.js | 020 |
data-operations/tests/integration/services/operations/promotion-import.integration.spec.js | 020 |
data-operations/tests/integration/services/queue/data-job-worker.integration.spec.js | 020 |
data-operations/tests/unit/api/data-job-submission-idempotency.spec.js | 020 |
data-operations/tests/unit/api/data-jobs-schemas.spec.js | 020 |
data-operations/tests/unit/operations/data-operations.spec.js | 020 |
data-operations/tests/unit/operations/error-classification.spec.js | 020 |
data-operations/tests/unit/operations/import-values.spec.js | 020 |
data-operations/tests/unit/queue/data-job-queue.spec.js | 020 |