---
kit_version: "1.0.0"
doc_id: "UMAY-DOC-08"
project_name: "UmayShop"
module: "08"
prepared_by: "compiled by example role"
content_owner: "To be assigned"
document_date: "2026-10-01"
status: "example"
language: "en"
revision_id: "en-example-r1"
source_revision_id: "example-r1"
translation_status: "machine_draft_reviewed_for_structure"
classification: "internal"
reference_eligibility: "example_only"
---
# UmayShop — 08. Delivery / Delivery and Logistics
> Translation note: This English machine draft preserves the source example snapshot. Language, publication and verification checklist values inside the example are historical sample content, not the current availability of this prototype. No human language signoff or real system verification is implied.
> **fictional example**: The text below is used to demonstrate how to fill out the template, and is not the actual implementation, permissions, deployment, or approval conclusion of UmayShop. Fictional examples cannot enter verified reference material.
Independently record the entire link from order placement to delivery, failure, and return shipment; order, payment, and logistics states are separated.
[Return to Main Table of Contents](../README.md) · [Unified Completion and Verification Rules](../AUTHORING-GUIDE.md)
## Table of Contents
- [Document Information](#文档信息)
- [Applicable Scope and Verification Conclusions](#适用范围与核验结论)
- [Participants and Handover Boundaries](#参与方与交接边界)
- [Forward delivery process](#正向配送流程)
- [State Dictionary and Transitions](#状态字典与转换)
- [Carrier Interfaces and Events](#承运商接口与事件)
- [Returns and Reverse Handover](#退货与逆向交接)
- [Exception Time Limits and Tracking](#异常时限与追踪)
- [Visual Charts](#可视化图表)
- [Sources, Final Decision, and Code Verification](#来源-最终决策与代码核验)
- [Attachments and Image Resources](#附件与图片资源)
- [Manual maintenance area](#人工维护区)
- [Language and Download Checks](#语言与下载检查)
- [Revision History](#修改历史)
- [Related Documentation](#相关文档)
## Document Information
| Field | Content to Fill |
| --- | --- |
| content owner / Confirmer | Pending assignment / unconfirmed; compiled by is not an automatic approver |
| Technical Lead / Target Deadline | Azong / 2026-10-19; template takes effect only after their confirmation |
| Template Version / Current Status | 1.0.0 / example; unreleased |
| Project / Compiled by | UmayShop / Example author role |
| Applicable Version / Environment | Example dataset r1 / fictional test environment |
| Code repository / Collection branch / Full fixed commit SHA | Real snapshot not obtained; fictional examples do not fill in fake fixed commit SHAs |
| Most recent confirmation time / Confirmation basis | Unconfirmed / Confirmation record not obtained |
| Access classification | internal: Internal; increase classification when restricted information is involved, inheriting source permissions |
| Language / source revision | zh-CN / example-r1; English and Russian not yet generated |
## Scope of Application and Verification Conclusion
| Item | Conclusion |
| --- | --- |
| Scope | Independently record the entire link from order placement to delivery, failure, and return shipment; order, payment, and delivery states are separated. |
| Collection exclusions | umay/cis-mep and all its subtrees are not collected, not translated, not exported, and not counted toward acceptance |
| Verified Scope | Provides fictional example entries only, private code unverified |
| Number of verified reference materials | 0; this document did not perform real Issue/source code verification |
| Evidence credibility level | Actual system conclusions: low/unknown; confirmed requirement scope: high (single user source, not code proof) |
| Limitations / Gaps | Need to supplement final decision, confirmed permissions, exact SHA, implementation location, and verification records; do not extend front-end static checks into back-end or production conclusions |
## Participants and Handover Boundaries
> Completion instructions: Logistics provider interface capabilities and manual operations are listed separately.
| Participant | Responsibility | Handed Over To | Handover Voucher | Implementation Method | Evidence |
| --- | --- | --- | --- | --- | --- |
| User / Web or Mobile | Submit order and shipping information | API-DEMO | Order confirmation record | Page request example | EXAMPLE-E08 |
| Warehouse | Picking, packaging, outbound warehouse processing | CARRIER-DEMO | Outbound warehouse processing order and handover vouchers | System + Manual | EXAMPLE-E08 |
| Logistics provider | Transportation and delivery | User / After-sales | Tracking and delivery receipt records | Callback example, manual exception follow-up | EXAMPLE-E08 |
## Forward Delivery Process
> Completion instructions: All steps must appear in the independent delivery diagram; payment confirmation does not equal outbound warehouse processing.
| Node | Entry condition | Action | Exit condition | Responsibility | Failure branch |
| --- | --- | --- | --- | --- | --- |
| Place order | Information valid | Create order | Order accepted | Example business role | Return for modification if validation fails |
| Payment confirmation | Order pending payment | Check payment result | Payment source confirmation | Example payment role | Keep pending payment on failure or close according to rules |
| Warehouse processing | Fulfillment permitted | Picking, packing, and re-checking | Generate outbound warehouse processing voucher | Example warehouse role | Short pick / damage handling |
| Carrier handover | Package ready for handover | Carrier receives | Handover credential confirmed | Example logistics role | Rejection enters exception |
| Transportation and receipt | Received | Tracking and delivery | Delivery evidence confirmation | Example logistics role | Delays/rejections/losses enter exception handling |
## Status Dictionary and Transitions
> Fill-in instructions: Do not concatenate states from different systems into an undefined enum. Provide the event and guard conditions (prerequisites allowing the transition) for each transition.
| State Domain | Original State | Target State | Trigger Event | Precondition | Source |
| --- | --- | --- | --- | --- | --- |
| Order example | CREATED | FULFILLING | Fulfillment permitted | Payment source confirmed | API-DEMO |
| Payment example | PENDING | PAID | Payment notification verification passed | Signature and amount match | PAY-DEMO |
| Warehousing example | PICKED | DISPATCHED | Outbound warehouse processing review | Quantity/package consistent | WMS-DEMO |
| Logistics example | IN_TRANSIT | DELIVERED | Valid delivery sign-off record | Chronological order and waybill consistency | CARRIER-DEMO |
## Carrier Interfaces and Events
> Instructions: Processing principles must be specified for late, duplicate, and out-of-order events; do not repeatedly write inventory based on the callback arrival count.
| Integration ID | Direction | Key Data | Authentication / Verification | Retry and Deduplication | Exception Handling |
| --- | --- | --- | --- | --- | --- |
| INT-EX-CARRIER | Backend to carrier | shipmentId, parcelId | See API-EX-02 | Query first on timeout; idempotency key | Manually verify orders with unclear results |
| EVT-EX-DELIVERY | Carrier to backend | eventId, trackingId, status, occurredAt | See directory 09 callback verification | eventId deduplication; status legitimacy verification | Old events are logged without reverting final states |
## Return Shipment and Reverse Handover
> Instructions: Return shipment, after-sales approval, refund, and inventory restoration are distinct actions and cannot be inferred from one another.
| Node | Input | Confirmation Condition | Output | Responsibility | Exception |
| --- | --- | --- | --- | --- | --- |
| Return shipment request | Reason / Order | Meets after-sales rules | Acceptance or rejection record | Example customer service role | Request supplement if materials are insufficient |
| Return shipment | Return waybill | Carrier receipt | Return tracking | Example logistics role | Enter investigation if lost |
| Warehouse acceptance | Return shipment physical items | Quality inspection and quantity confirmation | Can undergo inbound warehouse processing again or be quarantined | Example warehouse role | Damaged items do not automatically restore sellable inventory |
| Refund Processing | After-sales approval record | Payment channel verification | Refund result recorded independently | Example Payment Role | Transfer to manual on failure; do not assume refund upon return shipment |
## Exception Time Limits and Tracking
> Instructions: Fill in actual approved values for all time limits; sample values do not serve as SLAs (external service commitments).
| Exception | Detection source | Actual time limit | Next step | Receiving owner | Closure evidence |
| --- | --- | --- | --- | --- | --- |
| Tracking unchanged for a long time | Monitoring or manual feedback | Pending approval | Query carrier before deciding on compensation | Unassigned | Work order and processing results |
| Mutually contradictory states | Order/warehouse/logistics reconciliation | Pending approval | Freeze automatic final state updates and reconcile | Unassigned | Correction records |
## Visual Diagrams
Diagrams only represent the verified scope; each key connection should be linked to a source. This is currently a fictional example and does not prove actual deployment.
### Independent delivery process
[Maintainable diagram source](../assets/delivery.mmd) · [Standalone image](../assets/delivery.svg)
### Standalone Return Shipment Process
[Maintainable diagram source](../assets/returns.mmd) · [Standalone image](../assets/returns.svg)
## Sources, Final Decisions, and Code Verification
**Inclusion rules**: First confirm "what the final decision is", then verify "what the target version actually did". Issue closure, the latest comment, title, or "resolved" are not sufficient to pass. Same period only indicates candidate association, not that it has been implemented.
| Evidence ID | Source Type / Location | Read Snapshot / Time | Independence and Completeness | Current Status |
| --- | --- | --- | --- | --- |
| EXAMPLE-E08 | Fictional requirements description + fictional code clues | No actual snapshot | Reposts from the same source do not count as independent sources; missing attachments must be marked | example_only |
| Decision ID | Issue / Comment ID / Time | Final decision and scope of application | Confirmer and permission basis | Alternative / Conflict Record | Decision Status |
| --- | --- | --- | --- | --- | --- |
| EXAMPLE-D08 | EXAMPLE-ISSUE / EXAMPLE-NOTE / fictional point in time | Displays unknown delivery state, do not presume delivered (fictional example) | No actual authorized confirmation records obtained | Actual conflicts unknown | unresolved |
| Final decision ID | Repository / Branch / fixed commit SHA | Implementation file:line number / symbol | Test or verification method / result | Code status / scope | Verifier / Time | Discrepancies and formal introduction conclusion |
| --- | --- | --- | --- | --- | --- | --- |
| EXAMPLE-D08 | Not obtained, do not use fake fixed commit SHA | Real implementation location not obtained | Real verification not executed | unverified / none | unverified / unconfirmed | Must not be introduced; re-examine after supplementing evidence |
Decision status: `unresolved` (undecided), `confirmed` (validly confirmed), `superseded` (superseded). Code status: `unverified` (unverified), `partial` (partial only), `code_verified` (supported by fixed-version code), `runtime_verified` (tested and supported in target environment). **Static code support does not equal passing production execution.**
The following must be satisfied simultaneously: the final decision has been validly confirmed, there are no unresolved conflicts, relevant code coverage is complete, evidence is locatable, and manual verification records are complete, before it can be listed as verified reference material within its verified scope. Assertions involving deployment, permissions, or the real behavior of external services additionally require operational evidence from the corresponding environment. Historical decisions are retained as history and do not impersonate current rules.
| Gap ID | Missing evidence | Impact | Supplemental Owner / Deadline | Resolution Conditions |
| --- | --- | --- | --- | --- |
| GAP-08-01 | Real decisions and code snapshots | Cannot generate verified business conclusions | Pending assignment / Pending confirmation | Supplement and record verifier, time, scope, and result |
## Attachments and Image Resources
| Resource ID | Source / Ownership | Local Relative Path | Integrity / Read Status | Permission Boundary | Language Processing |
| --- | --- | --- | --- | --- | --- |
| delivery | tools/diagram_assets.py in this package (local diagram structure definition) | ../assets/delivery.svg + .mmd | Generated locally; XML verifiable | internal / no external download | Chinese inside image is untranslated; currently only Chinese diagram |
| returns | This package's tools/diagram_assets.py (local diagram structure definition) | ../assets/returns.svg + .mmd | Locally generated; XML verifiable | internal / no external download | Chinese text inside image untranslated; currently only Chinese diagram available |
Attachments must record the original file URL, file name, content checksum, read time, and access classification; access tokens or signed temporary URLs must not be saved. That a link can be opened does not mean the body has been read. Redirection to a login page, corruption, encryption, or unrecognized scans are all marked as unread. Converted text must link to original documents and images, without overwriting the originals.
## Manual Maintenance Area
To be filled: explanations, exceptions, and operational notes confirmed by the person in charge. Subsequent automatic updates must preserve this section; submit diffs when conflicting with new evidence, and do not silently delete. This initialization script will not update existing content.
## Language and Download Checks
| Check Item | Current Status / Requirement |
| --- | --- |
| Chinese source | This page is in Chinese; source revision fixed by revision_id |
| English / Russian | Not generated. Subsequent automated translations bind to Chinese source revision (source_revision_id); after the source text is updated, old translations are marked as stale |
| Content structure | Translation preserves heading hierarchy, table of contents, tables, code, links, fields, and numerical values; terminology follows the project glossary |
| Images and In-Image Text | Original images and local assets are retained; Chinese text inside images must be separately remade or provided with translation notes; untranslated images are not counted as complete translations |
| Markdown download | When images are included, download as a ZIP containing Markdown + assets + resource manifest; must not provide only invalid remote links |
| PDF Download | Platform must implement pagination, table of contents/bookmarks, tables, Chinese/English/Russian fonts, and local image embedding; missing images should block complete success |
| Export and permissions | Bind document revision, language, image version, and template version; inherit source permissions and do not disclose restricted content |
| Package capability boundary | Only generates Markdown document tree and local diagram source/SVG; does not perform translation, PDF rendering, login, or platform publishing |
## Revision History
| Revision | Date | Compiled by | Changes | Confirmation / Basis |
| --- | --- | --- | --- | --- |
| example-r1 | 2026-10-01 | Compiled by example role | Initialize fictional example | Unconfirmed / Template 1.0.0 |
## Related Documents
- [03. Backend / Backend Service](../03-backend/README.md)
- [07. WMS / Warehouse Management System](../07-wms/README.md)
- [09. API / Interfaces and System Integration](../09-api-integrations/README.md)
- [12. Monitoring, Logging, and Error Handling](../12-observability/README.md)