The BBD is usually recorded at the warehouse, but the platform's product page may have no date or may still show an old one. Opening product pages one by one by hand, checking them against the 3PL warehouse list and then typing in the dates becomes hard to sustain once there are many SKUs.
Why is there a gap between warehouse and platform BBDs?
Warehouse batch data and sales channel data are stored separately. One SKU can have several batches at the same time: older batches may have expired or already been dispatched, while the newer batch is the stock customers can still order. Without a batch-by-batch check, product pages easily get stuck on an old date.
What are the mapping steps?
- Upload the warehouse's stock-on-hand report; there is no need to export HKTVmall data separately, as the comparison uses the HKTVmall SKUs from the most recent sync in RAID.
- The system reads only the batch data rows and maps them to HKTVmall SKUs by Barcode.
- It compiles the comparison results, listing separately the items that can be updated, those that could not be matched and those that cannot be updated.
- The team reviews the change list, ticks only the items it trusts, and starts a promotion strategy where needed.
- Only after a second confirmation is the chosen store's product data updated.
Which batch's date should the product page show?
- The batch customers can still order is the one that counts; older batches that have expired or been dispatched and can no longer be ordered are skipped.
- If the earliest orderable batch has itself expired, the SKU is flagged and its update is paused, so that customers do not receive expired goods.
- When an update runs, the BBD field and the date in the product title are updated together so that they stay consistent.
When is nothing updated?
- The Barcode does not map to any HKTVmall SKU.
- The date in the warehouse data is not a valid date.
- The SKU ships from an HKTVmall warehouse, or its shipping method cannot be confirmed.
- The updated product title would exceed HKTVmall's title character limit.
Comparing, ticking items or downloading the Excel file never changes platform data. Only confirmed items are updated, and each result is listed item by item, whether it succeeded, was rejected or is still processing.
How does RAID handle this?
One-click BBD sync puts these steps on a single page: one upload of the warehouse stock report produces a BBD change list, updates happen only after the team confirms, and there are fewer gaps between warehouse batches and sales channel data.
Key points
- The Barcode is the bridge between warehouse batches and HKTVmall SKUs.
- The date shown follows the orderable batch; updates pause when the earliest orderable batch has expired.
- The BBD field and the date in the title are updated together.
- Every update needs the team to review and confirm the change list; the comparison itself never changes platform data.