zoe/ttx-project-doc
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: defer rack transfer outbound triggers

Browse Source
This commit is contained in:
曾志威
2026-06-04 15:47:07 +08:00
parent 1945b6057d
commit 74691bf665
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
superpowers/plans/2026-06-04-shopee-outbound-api-wes-mapping.md
+4 -2
View File
@@ -51,7 +51,7 @@ Do not implement inbound module interfaces in this plan. Include all concrete in
- Modify: `wms-wave/src/main/groovy/com/ittx/wms/wave/service/hairo/WaveRuleMatchService.groovy`
- Replace Shopee wave bind placeholder with a call to `edi-shopee` and parse failed shipment IDs.
- Do not modify WES transfer-order business hooks for `4.1` in this phase.
- Only implement the `4.1` interface surface and `edi-shopee` forwarding path; the real移库业务触发点 remains explicitly out of scope.
- Only implement the `4.1`, `4.6`, and `4.7` interface surfaces and `edi-shopee` forwarding paths; the real移库业务触发点 remains explicitly out of scope.
- Create only if no existing transfer service method is suitable: `wms-api/src/main/groovy/com/ittx/wms/api/service/platform/ShopeeRackTransferMappingService.groovy`
- Define `4.1`, `4.6`, and `4.7` request contracts and response normalization only; do not read `TransferOrderHeader`/detail data until the business trigger is confirmed later.
- Modify: `src/main/resources/application.yml` and profile-specific config only if no existing system-parameter path is available.
@@ -847,7 +847,7 @@ edi-shopee -> /api/wms/api/sync/in?api=<WES api>&format=json -> PlatformInboundA
Inside `ShopeeInboundApiHandler`, route to existing `wms-transfer` / `wms-inventory` services first. Do not add a separate WES controller for these four endpoints. Add new service methods only when existing transfer/inventory APIs cannot express the protocol action.
- [ ] **Step 4: Add 4.6-4.7 WMS-to-Vendor rack-transfer calls**
- [ ] **Step 4: Add 4.6-4.7 WMS-to-Vendor rack-transfer interface endpoints only**
Use internal `edi-shopee` endpoints for:
@@ -856,6 +856,8 @@ Use internal `edi-shopee` endpoints for:
| 4.6 | `/internal/shopee/automation/rackTransfer/queryPickingList` | `/api/v2/automation/tovendor/inventory/racktransfer/query_picking_list` |
| 4.7 | `/internal/shopee/automation/rackTransfer/updateRtOrder` | `/api/v2/automation/tovendor/inventory/racktransfer/update_rt_order` |
Do not bind these endpoints to WES对账任务、移库取消、优先级更新、人工操作 or any other business trigger in this phase.
Keep the `4.1` internal endpoint:
Use the same internal client pattern as wave-number and wave-bind calls: