Please enable JavaScript.
Coggle requires JavaScript to display documents.
Retail OMS System - Coggle Diagram
Retail OMS System
-
Main Features
-
-
Task automation
Reduce manual workload: order processsing, status update & communication
-
API intergration: Intergration across systems (Platform, OMS & WMS
-
Feature Questions
Pricing
- Bulk upload for invoice price by different client account
- For any price changing within a month, can adjust and update?
- System can realize and alert if lacked code between new commercial plan and old commercial plan
- Clients can view and check their price and ADA price by SKU levels before raise the PO.
- Any feature to alert clients in case of GAP price for confirmation and rejection after raise PO and remark to client new code to replace substituted code
- Can Export SO report with specific monthly commercial plan based on data range ?
Ordering/Key in
Any features for bulk upload PO:
- Maximum PO can be uploaded one time (Weekly B2B PO > 100 PO, each PO 10 - 80 SKUs)
- Upload timing and releasing the PO
- System can realize stock coming to set up key in time
- System will hold PO until stock inbounded or will release SKUs with enough stock first. Can be flexible customize timing release PO to WH to keep SLAs
- FFM check its impact for this feature
-
Delivery
Delivery: Feature to record delivery/loss at delivery. Whether can attach images/video as evidence
- HBOO: Delivery q'ty same as key in SO q'ty. Manual input drop at delivery and notification to check/feedback delivery issue between FFM & B2B
- TIKI: Delivery is recorded manually by accounting team. FFM/B2B will remark manually
-
- Feature to create and maintain B2B stores database: Store code, Address, Contact number
- Automated allocation delivery information after create the PO with specific store code number
- Notification to request new store code creation after new PO created
-
-
Code
- System has feature to maintain/update Tiki Master Combo SKUs?
- Tiki code - ADA code - Unilever Barcode
- Tiki/ADA combo SKU and its components & components q'ty (Primary bundle and Secondary bundle)
- System can transfer from Tiki code to ADA code & Unilever barcode or import by ADA code only (Single, Primary combo "X", Secondary virtual combo "_")
For Tiki combo SKUs bundled by ADA:
- System can break ADA combo SKUs to its components and quantity, ADA Planning team raise PO by single SKUs
- If not, need break manually to components before import to system?
- System can realize combo SKUs to book VAS if available SOH of its component single SKUs when key in system or need to inform FFM to proceed VAS in advance?
SC Code status to define outbound full/lose carton accordingly:
- Active: accept the PO 'qty and round full carton. Check insufficient SOH and alert to planning team
- In-active: accept within limit SOH and accept lose carton. Alert to get approval lose carton fees