JINGDONG logistics RLC

Reverse Logistics Control

run

Today's work

what needs doing, in the order it will cost you money
press / to jump here

By carrier

open volume and the oldest case

Needs identifying

no carrier we have a process for

Master database

built to spec §6

Refresh the data

files stay in your browser
Drop today's exports here. Each file replaces only its own source, so the rest of the database stays as it is. Nothing leaves your browser. Recognised: After Service Order, Return Inbound, pickup report, insite rejected, AIT job query, AIT mapping, AIT claims, BJS master, warehouse register (any sheet named “Customer Return”), waybill mapping (any sheet with a FOP order column and a waybill or tracking column).
Drop .xlsx or .csv files here, or click to choose

Reference

how each status is decided
Received at warehouse — IFOP inbound is 70/Completed. This is the only status that means the unit is physically checked in.
Collected — after-sales order with a Pickup Time in the TMS pickup report. Depot and driver shown.
Rejected at door — reject order with a Refused Time in the TMS insite report. Depot, courier and refusal reason shown.
Pickup failed — TMS recorded a Pickup Termination Time; reason shown. Needs rebooking.
On route — matched in TMS with an expected pickup date but no collection or refusal yet. Expected date shown so you can see what's due.
Correcting a reference \u2014 open a case and edit the waybill or carrier ref in the Reference block. The correction is kept separate from the imported file and re-applied at the start of every rebuild, so it survives a data refresh and it re-runs carrier identification and feed matching rather than only changing what is displayed. The original value is kept and shown, Revert puts it back, and corrected cases carry a Manually corrected column in exports. Corrections are held on this machine, like the chase log.
Back with us \u2014 WH to locate — the carrier’s own status is “Returned to Client”, or the AIT manifest hunt shows they sent it back. They have returned it to us, so this is a warehouse search, not a claim, and no claim is raised against the carrier.
Awaiting TMS — 1PL order exists in IFOP (usually 20/Released to warehouse) but nothing in either TMS report yet.
Two different processes, by carrier1PL is our own vans, so there is nobody to claim against: if a return is not back after 3 days we ask the warehouse to check, and past 9 days it becomes a warehouse search. AIT and BJS are third parties who collected our stock, so if they lose it we claim: chase from 11 days, and the claim must be raised inside the 14-day window or the carrier can refuse it. The Claim window column shows own fleet for 1PL because the concept does not apply. Chase emails and claim text are generated for AIT and BJS only.
How carrier is decided — IFOP holds the carrier's own reference in the tracking field and the universal JoyBuy waybill separately. An 8-digit reference is AIT, B0000000-0000 is BJS, XLC… is XLC, and a JDW… reference means JD's own network (1PL). Where the reference is blank the waybill is looked up in the AIT and BJS feeds before falling back to Unknown — a JDW waybill on its own does not prove 1PL, because AIT and BJS orders carry JDW waybills too.
Outstanding with carrier — a non-1PL return that IFOP still shows as open and that no carrier feed covers yet. Track on Order age and chase the carrier.
Where receipt comes from — the depot return register has been retired: it covered 1PL only, was hand-maintained, and its receipt column contradicted both FOP and the carriers. FOP is now the single authority. A case at 70/Completed counts as back at the warehouse; anything else does not. If a carrier says collected and FOP says completed, the case is closed.
Claim on carrier — on the AIT Claims to raise sheet. The carrier still holds it or has lost it, so the claim goes to them.
Arrived at Depot Awaiting Receiving Process — the warehouse register confirms the parcel is in our building but FOP is still open, so nothing is at risk and nobody needs chasing: something is blocking the booking-in, most often a label that will not match the order. This covers every carrier, because a parcel sitting on our own shelf is a warehouse job whoever delivered it. Cases where FOP has since closed at 70/Completed drop off automatically.
Back with us, not found — the carrier's status is Returned to Client, and we are the client, so it has already been sent back to us. Nothing shows against it on the warehouse register, which means it is on our side and simply cannot be found. No claim is raised for these, because the carrier has done its part — the copy-claim button is deliberately hidden. The next step is the carrier's return manifest for that date, then a warehouse search.
Needs identifyingNone, Unknown, Other, XLC and ZR/XF grouped together. The tracking reference does not identify a carrier we hold a process for, so no claim window and no chase route applies until someone resolves them.
Claim already raised — the AIT note records a claim as submitted, so no new action, but it is still outstanding until the stock or credit lands.
No tracking number — IFOP order is open but has no tracking reference at all, so no carrier can be identified. These need a number assigning before anything can move.
Cancelled — IFOP status 90/Canceled or 91/Cancel failed.
Aging — days since collection/refusal for anything not yet received at the warehouse.