---
kit_version: "1.0.0"
doc_id: "UMAY-DOC-07"
project_name: "UmayShop"
module: "07"
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 — 07. WMS / Warehouse Management System

> 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.

Map inbound warehouse processing, storage, picking, outbound warehouse processing, and inventory movements to online/offline handovers.

[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](#适用范围与核验结论)
- [Warehouse modules and documents](#仓库模块与单据)
- [Inbound Warehouse Processing to Outbound Warehouse Processing Flow](#入库到出库流程)
- [Inventory Quantities and Change Rules](#库存数量与变动规则)
- [Integration and Data Exchange](#集成与数据交换)
- [Exception Operations and Handover Responsibilities](#异常作业与交接责任)
- [Sources, Final Decision, and Code Verification](#来源-最终决策与代码核验)
- [Attachments and Image Resources](#附件与图片资源)
- [Manual maintenance area](#人工维护区)
- [Language and Download Checks](#语言与下载检查)
- [Revision History](#修改历史)
- [Related Documentation](#相关文档)

<a id="文档信息"></a>

## 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 |


<a id="适用范围与核验结论"></a>

## Scope of Application and Verification Conclusion

| Item | Conclusion |
| --- | --- |
| Coverage scope | Map inbound warehouse processing, storage, picking, outbound warehouse processing, inventory movements, and online/offline handovers. |
| 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 |


<a id="仓库模块与单据"></a>

## Warehouse Module and Documents

> Fill-in instructions: Warehouse operations do not necessarily all have system interfaces; system operations or manual SOPs (standard operating procedures) must be clearly stated.

| Module | Document / Task | Purpose | Operating Role | Online / Offline | Evidence |
| --- | --- | --- | --- | --- | --- |
| Inbound warehouse processing | ReceiptDemo | Count and register inbound arrivals | Example receiving clerk | Manual verification + system registration | EXAMPLE-E07 |
| Storage bin | BinDemo | Place goods in designated location | Example warehouse clerk | Manual operation + bin record | EXAMPLE-E07 |
| Picking / outbound warehouse processing | PickDemo / ShipmentDemo | Pick and review by order before handing over to carrier | Example Picker / Reviewer | Mixed | EXAMPLE-E07 |


<a id="入库到出库流程"></a>

## Inbound Warehouse Processing to Outbound Warehouse Processing Flow

> Completion instructions: Explain step by step the inputs, outputs, states, preconditions, and exceptions; do not treat scanning actions as logistics delivery.

| Step | Precondition | Input | Completion output | Example status | Exception next step |
| --- | --- | --- | --- | --- | --- |
| Inbound warehouse processing count | Arrival order registered | Items, quantities | Discrepancy check record | RECEIVED | Quantity mismatch enters discrepancy processing |
| Storage shelving | Inventory check passed | Goods / storage location | Storage location allocation record | STORED | Suspend shelving if no storage location is available |
| Picking | Outbound warehouse processing task authorized | Picking task | Actual picked quantity | PICKED | Short picking rechecks inventory |
| Recheck outbound warehouse processing | Physical goods match documentation | Package / waybill | Outbound warehouse processing handover evidence | DISPATCHED | Do not mark handover completed without carrier confirmation |


<a id="库存数量与变动规则"></a>

## Inventory Quantities and Change Rules

> Completion instructions: Distinguish between on-hand, locked, available, and in-transit; formulas and accounting timestamps require dual confirmation from both code and warehouse.

| Quantity item / Operation | Example definition | Trigger document | Deduplication key | Audit / Reconciliation |
| --- | --- | --- | --- | --- |
| Available quantity | Example max(on-hand - locked, 0) | InventoryDemo | None | Real formula to be confirmed |
| Receiving +10 | Increase on-hand inventory after count passes | ReceiptDemo R-EX-01 | receiptId + lineId | Record quantity values before and after |
| Outbound warehouse processing -2 | Reduce on-hand inventory after handover recheck | ShipmentDemo S-EX-01 | shipmentId + lineId | Verify against shipping order |
| Inventory count adjustment | Record variance after approval, do not directly overwrite history | AdjustDemo A-EX-01 | adjustmentId | Retain reason and approval records |


<a id="集成与数据交换"></a>

## Integration and Data Exchange

> Completion instructions: Specify protocol, frequency, fields, errors, and replay strategy for each handover target.

| Peer | Purpose | Data | Method | Failure / retry | Content owner |
| --- | --- | --- | --- | --- | --- |
| API-DEMO | Send outbound warehouse processing progress | eventId, shipmentId, status | Asynchronous event example | Deduplicate duplicate events; retain failures for pending processing | Example backend role |
| CARRIER-DEMO | Create handover request | parcelId, weight | Interface example; see Directory 09 for details | If result is unknown, query first; do not blindly place duplicate orders | Example logistics role |


<a id="异常作业与交接责任"></a>

## Exception Operations and Handover Responsibilities

> Completion notes: There must be an explicit handler when discrepancies occur among inventory, physical goods, and documents.

| Exception | Discovery node | Freeze or isolation scope | Handling method | Handover voucher | Content owner |
| --- | --- | --- | --- | --- | --- |
| Short pick | Picking | This outbound warehouse processing task | Reschedule after verifying storage location and inventory | Exception sheet EX-01 | Example warehouse role |
| Damaged | Receiving or return shipment | Issue items | Quarantine for inspection, do not directly add to sellable inventory | Photo reference (no privacy details) | Example QC role |


<a id="来源-最终决策与代码核验"></a>

## 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-E07 | Fictional requirements description + fictional code clues | No real 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-D07 | EXAMPLE-ISSUE / EXAMPLE-NOTE / fictional time point | Display unknown delivery state, do not presume delivered (fictional) | Authentic authorized confirmation records have not been obtained | Actual conflict 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-D07 | 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-verify 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-07-01 | Actual decisions and code snapshot | Cannot generate verified business conclusions | Pending assignment / Pending confirmation | Complete and record verifier, time, scope, and results |


<a id="附件与图片资源"></a>

## Attachments and Image Resources

| Resource ID | Source / Ownership | Local Relative Path | Integrity / Read Status | Permission Boundary | Language Processing |
| --- | --- | --- | --- | --- | --- |
| Sample Attachment | Original attachment not provided | Not acquired | Not read, not included in verification | Inherits Issue and attachment access scope | Translations and resources not generated |

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.


<a id="人工维护区"></a>

## Manual Maintenance Area

<!-- MANUAL:START -->
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.
<!-- MANUAL:END -->


<a id="语言与下载检查"></a>

## 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 |


<a id="修改历史"></a>

## 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 |


<a id="相关文档"></a>

## Related Documents

- [08. Delivery / Delivery and Logistics](../08-delivery/README.md)
- [09. API / Interfaces and System Integration](../09-api-integrations/README.md)
- [10. Databases and Data Models](../10-database/README.md)
- [12. Monitoring, Logging, and Error Handling](../12-observability/README.md)