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

docs: confirm rack transfer inbound handling

Browse Source
This commit is contained in:
曾志威
2026-06-04 15:46:01 +08:00
parent 83190243e2
commit 1945b6057d
1 changed files with 7 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
+7 -2
View File
@@ -25,6 +25,7 @@ Do not implement inbound module interfaces in this plan. Include all concrete in
- `SyncApiController` already receives standard platform calls and delegates through `ApiService`; this remains the internal WES target called by `edi-shopee`.
- `ApiService` already delegates `ess.*` and `shopee.*` APIs to `PlatformInboundApiService`.
- `ShopeeInboundApiHandler` exists but has no outbound cases implemented.
- Confirmed: `4.2`-`4.5` Vendor-to-WES inventory/rack-transfer interfaces all enter WES through `ShopeeInboundApiHandler`; the handler then reuses existing `wms-transfer` and `wms-inventory` services.
- `ShipmentHeader` already contains key Shopee fields: `cutOffTime`, `purchaseTime`, `orderTime`, `shopeeWave`, `waveRule`, `kickOutWave`, `ticketType`, `pickType`, `orderStructure`, `groupKey`.
- `ShopeeWaveService` has low-water scheduling and persistence, but the actual upstream wave-number request is still a placeholder.
- `WaveRuleMatchService` has Shopee wave binding placeholders and local binding/rollback logic.
@@ -831,7 +832,11 @@ Keep `ticket_type = 6` fixed for Rack Transfer. The later WES business trigger w
- [ ] **Step 3: Add 4.2-4.5 Vendor-to-WES rack-transfer handlers**
Expose these Shopee-facing `edi-shopee` endpoints and forward them to WES `ShopeeInboundApiHandler`:
Expose these Shopee-facing `edi-shopee` endpoints and forward them to WES sync API with the WES api name below. WES dispatch must be:
```text
edi-shopee -> /api/wms/api/sync/in?api=<WES api>&format=json -> PlatformInboundApiService -> ShopeeInboundApiHandler
```
| Section | Path | WES api |
| --- | --- | --- |
@@ -840,7 +845,7 @@ Expose these Shopee-facing `edi-shopee` endpoints and forward them to WES `Shope
| 4.4 | `/api/v2/automation/toshopee/inventory/racktransfer/sync_picking_sku_list` | `shopee.inventory.racktransfer.syncPickingSkuList` |
| 4.5 | `/api/v2/automation/toshopee/inventory/racktransfer/handle_diff_stock` | `shopee.inventory.racktransfer.handleDiffStock` |
Route to existing WES transfer/inventory services first. Add new service methods only when existing transfer APIs cannot express the protocol action.
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**