Tracking broke and the buyer chases: face which waybill and which track, do not reply arrived from memory

A Durban flour mill’s on-site original at 08:05 Friday: “Where is the 20GP of 25kg kraft valve sack 50×80cm. Tracking stopped. Last time your truck was already in Durban. Confirm arrived today. We mill Monday. I did not lock the next 20GP.” Sales replied from last-ticket memory: already at Durban port, will deliver Monday. Buyer WhatsApp: “Our warehouse did not see the box. You confirmed arrived. We booked casuals.” The forwarder last hop still sat at Singapore outer anchorage.

Memory two words do not fill this ticket’s track. Membership paid to ALIBABA.COM HONG KONG LIMITED does not put the box in Durban by itself, and it does not buy an official arrival time. Corpable Marketing Limited does not check the vessel for you, and does not guarantee a berth this week.

How shipping proof is submitted: Trade Assurance shipping proof. Alibaba Logistics or your own forwarder: which channel. Fees after the box arrives: demurrage and detention. How to split freight out of an inquiry: inquiry freight. Below only this: the track broke, they chase arrived, and the number in the clip has not been faced.

Which waybill and which track this ticket clip holds now

Open this ticket’s clip. BL number, container number, courier waybill — copy as many as there are. Sales saying “the forwarder sent a number in the group” does not replace the slip in the clip.

My Alibaba → this Trade Assurance order’s logistics or shipping info. Read whether the platform number and the clip are the same slip. They are not: write “platform number and clip do not face,” pick which one governs, write it back on this thread.

A sub-account can see the inquiry and cannot see the logistics cell. The account that can open order logistics governs. The sub-account says there is no number. The main account still searches the order number.

25kg valve sack 50×80cm. Marks still print a neighbour 20kg. Marks wrong and the track faces the wrong goods. This thread asks the marks first. It does not reply arrived first.

How-to-sell writes reply soon. Reply soon is this ticket’s number and the last hop, not arrived faster.

The clip only has a forwarder WeChat crop. No carrier-site screen. A crop may staple. The site still opens. The crop is Wednesday. They chase Friday. The crop is stale.

Same buyer, two tickets: the valve-sack ticket is ocean, a sewing-thread sample is courier. Chasing the 20GP faces the BL. Face the courier and the Durban warehouse will wait at the door for an envelope.

The shop lead audits whether the clip cover shows this ticket’s BL. No number: duty may not open their mouth on arrival.

Whether the BL in the clip is telex or original is not the same sentence as the track. Telex proves release can happen. It does not prove the box is in Durban. Release terms sit on a BL page. Here you only face the last hop.

The order logistics cell is missing one digit. One digit short and the carrier site opens someone else’s box. The person who copies the number reads it back. The read-back writes on the clip cover.

The 25kg valve sack’s batch prints at the mouth. The track broke. They want a mouth photo first to prove the goods are on a vessel. A photo is not a track. A photo may go in a note. It does not replace the carrier site.

An ocean BL and a courier number are not the same track

The 20GP faces the BL and the container number. A sample faces the courier waybill. Two tracks do not fuse into “the goods are already on the way.”

The forwarder dropped a courier number into this ticket as if it were the box. Digit count and format do not face a BL. They do not: treat it as the wrong number. Reply on this thread: this number is not the ocean BL.

Alibaba Logistics back office may mint a platform tracking number. Click in and read the mapped carrier number. The map empty: the platform number does not fill the carrier site. The site will not open: do not reply arrived.

Your own forwarder and Alibaba Logistics each have a set of numbers. Which set this ticket uses staples onto the clip cover. Reply both and they will bookmark the short arrived.

The shipping-proof page covers how a number is submitted. A submitted number is not arrival. A rejected proof sits on the proof page. Here you only face the last hop.

Container number faces, BL wrong: the site opens someone else’s box. Someone else’s box in Durban is not your 50×80. Face the container number before you open your mouth.

Night sent a courier query link to the mill. The link opens the sewing-thread sample. The sample arrived. The box did not. The warehouse will roster Monday casuals as if the box arrived.

The forwarder sent a booking number into this thread as a BL. A booking often will not resolve on the carrier site. It will not: reply this is the booking, not the BL. Do not use a booking to reply already on water.

Container number faces. Seal was not copied. A seal is not arrival. After arrival the warehouse will check the seal. Seal not copied: add it to the clip. Still do not reply arrived.

Alibaba Logistics’ “in transit” colour block parks waiting-to-load and already-loaded together. Click in and read the hops. Do not translate the colour block yourself. A colour block does not fill Durban.

Track stopped at the last port — do not reply already in Durban

The carrier last hop writes Singapore anchorage or equivalent. Reply it sits there, with the time. Do not translate it into in transit to Durban so they hear almost there.

In transit four words are too wide. A wide word locks an outward arrival expectation. This ticket only locks the last-hop place name.

Last time your truck was already in Durban. Last time’s truck is not this ticket’s vessel. Reply on this thread: that was another BL. The other BL number may sit there too, so they do not query the old one.

We mill Monday. A mill-start day is not an arrival day. A mill-start may go in a remark. Written into the reply as a promise, it locks Monday delivery outward.

Confirm arrived today. Today two words lock. The site does not show discharged / gated in. Today does not go out.

The track has not moved for three days. Ask the forwarder for a carrier note. The note writes back on this thread. No note: only repeat the last hop. Do not add clearance in progress.

Durban congestion, weather, a short-ship: this page does not invent a reason. No carrier writing, sales must not invent one.

Already replied arrived. The next sentence may only withdraw: previous arrived was wrong, last scan is …. No withdraw and casual wages will face you.

Demurrage has not started. The box is not there. Do not quote demurrage days first. A later demurrage page will read the actual empty-return day.

Singapore outer anchorage has sat four days. Four days is not arrival. Ask the forwarder for carrier writing. No writing: repeat the anchorage. Do not add typhoon, strike, short-ship — words with no paper.

The site time is UTC. The Durban warehouse runs South Africa time. The last-hop reply carries a zone, or writes the site’s original time. No zone and Monday will roster on their Monday.

The track shows discharged and still sits in Singapore. Discharged is not Durban. The place name must show Durban or the matching terminal code. It does not: arrived does not go out.

They send a vessel AIS crop. The icon sits off Durban. AIS is not this container number. The vessel arrived. The box may still sit at the last port. Reply on this thread: AIS is the vessel, we face this container number.

Buyer chases from last-ticket memory — what this original writes back

Open this message-centre thread. Read the original from the top. The original wants this 20GP, this 50×80. Last ticket’s 20kg sack is not this ticket.

The first sentence carries this BL, the container number, the carrier last hop. Do not open a side “friendly update.” A side note and handling will not face this ticket.

WhatsApp may carry the same carrier screen. This thread must open the same crop. It lives only in a phone album. Compressed, the container number is unreadable. That equals not replied.

Two rounds of only arrived? arrived?. Two rounds still face the last hop. Do not switch the third to Monday for sure to stop the chase.

I did not lock the next 20GP. The next box is unlocked. This track replied: do not casually quote the next box’s vessel. A vessel locks outward.

The mill warehouse mailed separately asking for a truck plate. A plate faces the carrier’s dispatch note. No dispatch note: reply there is still no land dispatch. Invent a plate and the gate faces empty.

Sales wrote “should be soon” into the shop group. The shop treats arrival as done and stops the back process. The back process stopped, the sacks still sit at anchorage, and Monday the mill waits empty.

Purchasing wrote tracking stopped. The Durban warehouse mailed separately asking for a portal booking. A booking faces carrier dispatch. No dispatch: reply there is still no land booking. Invent a booking number and the gate faces empty.

Original: I did not lock the next 20GP. This track replied. Sales must not write a pre-allocated vessel for the next box to look easy. A pre-allocated vessel locks outward.

The same arrived? two rounds. The third adds we will claim. Claim sits on the dispute page. The track still sits at anchorage. Do not pre-write a defence. Reply the last hop, and staple both originals to the shop lead.

They paste last ticket’s WhatsApp crop. The crop shows already in Durban. An old crop is not this ticket. Reply this screenshot is another BL, this ticket’s last scan is ….

Who opens the logistics page, who clicks the carrier site

Merchandising opens the order logistics cell and the number in the clip. The forwarder or documents opens the carrier site. Sales does not invent arrival.

The site will not open. Write open failed and which number was tried, back on this thread. Do not switch to a forwarder mouth. A mouth is treated as unchecked.

The platform logistics page updates slow. The carrier site already has a new hop. The later hop governs. Both screens staple into the clip. Staple only the platform and you will miss the site.

Only the main account can click shipping proof. The person who clicks proof is not the person who replies arrived. After the click you still read the track. A green proof does not cover the port.

A membership receipt covers a Durban berth even less. An advisor on the page only reads the number in the clip, the carrier last hop, and whether arrived already went out. It went out: withdraw first. Corpable does not check a vessel schedule.

Membership still goes to ALIBABA.COM HONG KONG LIMITED.

Night may only repeat the last hop already stapled in the day clip. Clip empty: they may only say the main account will check the site. They may not report Monday.

Forwarder night shift changed people and spoke a new container number. The new number is not in the clip. Day still replies the old one. The old one already closed on the site: write number pending check. Do not use a spoken new number to reply arrived.

Who clicks refresh on the platform logistics page: the person who can open the order. After refresh the site still opens. Refresh only the platform and a hop a day late will be treated as latest.

Finance wants to book “in transit” as delivered in the monthly. Internal in-transit may. Outward still follows the last hop. Internal in-transit does not cover a Durban discharge.

How-to-sell does not write memory as arrival

How-to-sell proves delivery is talked after payment. It does not audit this BL, and it does not write last-ticket memory as arrived. The buyer story proves handling reads the online order and the communication. It does not prove arrived inside a chat can swap the box. The dispute page proves the defence door. The track has not broken into a dispute. Do not pre-write a defence.

Keep for the review: this BL, the container number, the carrier-screen time, whether arrived already went out, whether a courier number was used as a box number, whether the mill rostered casuals on Monday. Weekly review reads whether the last hop moved, not how many chase mails you sent.

Conditions follow the order logistics and the carrier site you can open on 2026-10-18. The last hop is there: a person may reply. The hop is not there: face the number first. They do not face: do not say outward the box is already in Durban.

The forwarder only sends a new number Monday. The new number is not in the clip. Day still replies the old one. The old one already closed on the site: write the number changed, new number pending staple. Do not use the old number to reply arrived and paper over it.

If pallets sit in the box, the warehouse asks whether there are pallets. Pallets are not a track. Track replied: pallets ask the packing list. The list has no pallet: do not say pallet already arrived.

They forwarded your arrived into their union group. The group starts Monday. The withdraw must write back on this thread and the mail. Change only WeChat and the group still sits.

Ops weekly writes “one box arrived this week.” Arrival faces discharged on the carrier site. Anchorage does not count. Write it wrong and the owner will chase the balance as already delivered.

The next 20GP is unlocked. Ads must not add Durban stock. Stock written outward and an unarrived 20GP is also read as on-hand.

A new salesperson takes over with no carrier screen. They may only ask this BL. They may not say our schedule is stable. Stable is often last ticket’s memory.

Already replied Monday deliver. The next sentence may only become last scan …, delivery not confirmed. Two dates live and the mill rosters the earlier day.

Documents dropped a BL copy into this thread as “proof it arrived.” A copy proves this slip exists. It does not prove the box is in Durban. A copy and the carrier site are two screens.

If the valve sack has an inner liner, the warehouse asks whether the liner arrived. A liner is not another slip. It is another sentence. The track replies the box. Whether a liner sits: open the packing list. The list has none: do not say liner already arrived.

Durban customs pulled the box at the terminal. No hold writing: do not reply clearance done. Done two words lock. Writing arrived: write it back on this thread. Still do not translate it into arrived at mill.

Sales posted arrived to Moments. A Moments cover is not the carrier site. A mill peer sees “another box in” and the warehouse rosters people. Delete that post, or change it to the last-hop fact.

This 20GP’s VGM and the track are not the same cell. VGM proves a weight was declared. It does not prove the box is in Durban. A weigh slip may go in the clip. It does not enter the arrival sentence.

The next box is unlocked. The shop asks whether to stage the next valve-sack run for Durban. Staging follows an order. A broken track is not a reason to add production. An unlocked 20GP does not write into a shortage table to scare the owner.

Documents dropped a manifest copy into this thread as “the vessel already arrived.” A manifest proves this cargo name exists. It does not prove the last hop. A manifest and the carrier site are two screens.

Monday another mailbox asks same container?. A new mailbox is another conversation. Write the container number and the carrier screen back on this old thread, and write the same order number. The new conversation has no number. What they bookmark is arrived with no container.

Ops copies a neighbour shop’s arrival day under “same vessel hot.” The neighbour vessel is not this container number. A copied date locks outward. This ticket only needs the last hop visible.

Monday the mill wants a trial run. Purchasing is urgent. Urgent does not fill a track. Urgent may write back on this thread. It may not write into arrived. A trial-run day is not an arrival day.

Valve orientation had a packing ask. Orientation is not a track. Track replied: orientation opens the packing photo. No photo: do not say orientation already packed to Durban habit.

The forwarder wrote “ETA Durban Friday” into the group. An ETA is not a last hop. An ETA may sit internal. Written onto this thread, Friday locks outward. The site has no written ETA: the group’s Friday does not go to the buyer.

If this 20GP mixed a neighbour sewing-thread. Mix is not why the track broke. The warehouse will still look for the thread as if the box arrived. The box is not there: do not reply the thread is already in Durban. The thread’s courier number faces separately.

Sales asked the ship agent on a personal WeChat for a “spoken arrival.” A spoken arrival does not cover the carrier site. Staple the spoken as progress and afternoon the vessel still sits at anchorage. They will say you already confirmed.

The Durban warehouse booking system needs a container number. The number faces, the track is not discharged: the system refuses the booking. A refuse is not your fault. Reply on this thread: appointment needs discharged scan, last scan is …. Do not reply already discharged to force a booking.

The BL discharge port writes Durban. The vessel actually hangs Richards Bay. The port changed and the site hops to another port. It hops: reply the new port name. Do not still reply Durban arrived to please the contract.

Night saw an AIS icon near Durban and casually replied almost there. Almost two words lock an outward expectation. AIS near is not this container discharged.

Finance applies to pay the freight balance as “already arrived.” Freight pay follows the contract node. If the node is discharged and the site has no discharged, do not apply. Applied and the book follows arrived.

The next box is unlocked. The ad creative still writes Durban 7 days. Taking the creative down sits on the bid page. The track broke, the creative did not change, and what clicks in still sees 7 days first. First sight locks outward.

They dropped the track crop into their WhatsApp group. Another China supplier sits in that group. The other replies we can deliver faster. Faster in the group will drag this thread into another lead-time change. You reply on this thread with your own carrier screen. You do not enter that group to argue.

Documents dropped an insurance policy into this thread as “the goods are already covered to Durban.” A policy proves cover exists. It does not prove the box is in port. Insurance and the carrier site are two screens.

The shop asks whether this valve-sack run still opens paper this week. Opening paper sits on the order page. A broken track is not delivered. Paper follows a paid, undelivered order. Here you only stop one sentence: do not stop the back process, or add the next box, from already arrived.

The shop-lead weekly scores “boxes arrived this week.” The count includes anchorage. Anchorage lists apart. List it as arrived and sales will reply arrived to the buyer. Arrived two words have to face discharged.

A new mailbox asks payment against arrival. Arrival-pay is another sentence. This track is not discharged. Do not bind payment and arrived in one reply. Bind them and they treat you as already admitting arrival.

A humidity cert travels with the box. A cert is not a track. Track replied: the cert opens as a packing-list attachment. No attachment: do not say the cert already arrived at the Durban warehouse.

The forwarder sent a telex crop. Telex proves release can happen. It does not prove the box is at the terminal. Telex and discharged are two hops. Only telex: arrived still does not go out.

Friday their union already rostered people on your Monday. Withdrawing Monday writes to purchasing and the warehouse, two mailboxes. Write only purchasing and the warehouse still opens the door Monday.

The 20GP seal photo was taken the load day. A load photo proves it was loaded. It does not prove it is in Durban now. A photo may go in the clip. It does not enter the arrival sentence.

Sales wrote “vessel name + Durban” into the welcome auto-reply. An auto-reply locks outward. This track broke. The auto-reply still says Durban. This week that welcome sentence stops first.

The container number returns two results on the carrier site. One is an empty return. A return box may also have hung Durban. Face the booking date and the cargo name. They do not face: treat it as the wrong box. The wrong box’s discharged cannot stand as this arrival.

Merchandising slotted an unarrived paper manifest on the warehouse “to-unload” rack. People at the rack hold a truck for unload. The slip must show the last hop is not Durban, or that slip should not sit on the to-unload rack.

They want track authority so they can query themselves. Authority may. After authority you still reply on this thread from the carrier site. They see AIS near. AIS near is still not discharged.

The next box is unlocked. Finance fused this freight and the next freight into one “Durban project.” Project two words become both boxes already arrived. Freight splits on this ticket’s number. It will not split: do not reply the project arrived.

Night, the Durban warehouse calls asking for the driver. A driver is the land leg. The site still sits at anchorage. The land leg has no driver. Reply there is still no dispatch. Invent a driver and the gate faces empty, and the warehouse waits as if arrived.

If the valve sack wants a pallet, a pallet is packing. The packing list has no pallet and after arrival the warehouse will refuse the fork. A refuse is not a broken track. Track replied: pallets ask separately. Do not reply pallet already arrived to buy the warehouse opening the door.

The forwarder dropped a BL copy watermarked copy into this thread. Copy proves this slip exists. Copy is not discharged. Copy and the carrier site are two screens.

Durban free time has not started counting. The box is not discharged. A free-time sentence does not write first. A later storage page will read the actual day. Write it first and they read already at the terminal.

Sales sends last time’s truck photo again. An old photo locks as this ticket’s arrival. The plate on the old photo is not this dispatch. The old photo does not go out.

Monday you find last week already replied arrived. The mill’s casuals waited empty a whole morning. Note the empty wait. The next sentence may only withdraw and staple the carrier site. Do not use this once to change shop rule into “reply arrived, then backfill the track.”

Paper gsm was not locked in the original. Gsm is not a track. Track replied: gsm opens the order row. The row has none: do not say the 25kg sack already arrived to a Durban standard.

The shop lead audits three screens: this BL, the carrier last hop, whether this thread already replied arrived. Three screens do not face: sales must not report the box already in Durban. In Durban two words have to face discharged.

The mill warehouse wrote your arrived into their receiving plan. The plan does not change and Monday’s people will come. The withdraw must make them change the plan. Change only this thread and the plan still sits.

Whether this 20GP is a standard or a high cube was not locked in the original. Box type is not a track. Track replied: box type opens the booking. The booking has none: do not say a high cube already arrived in Durban.

An advisor on the page only reads the number in the clip, the carrier last hop, and whether arrived already went out. It went out: withdraw first. Corpable does not check a vessel, and does not guarantee a berth this week. The hop sits at anchorage: say anchorage. Do not say Durban. Do not say Monday delivery. Do not say a truck already at the mill door. Memory does not fill this container number, and it does not fill a Durban terminal. The hop sits where it sits. Reply that port. Do not translate for the carrier.

Conditions still follow this ticket’s number and the carrier site you can open on 2026-10-18. The hop sits at the last port: say the last port. A truck from memory does not write onto this thread.

Conditions still follow this ticket’s number and the carrier site you can open on 2026-10-18. The hop sits at the last port: say the last port. A Durban truck from memory does not write onto this 50×80 valve-sack ticket.

Questions teams actually ask

Related reading

• Trade Assurance shipping proof
• Alibaba Logistics or your own forwarder
• Demurrage and detention
• How to split inquiry freight
• Contact Corpable · info@aliad.hk

Written by Corpable Marketing Limited for Alibaba.com Hong Kong-channel sellers. Not legal, tax, or audit advice. Platform, customs, bank, and auditor outcomes follow the latest official notices. Membership fees go to ALIBABA.COM HONG KONG LIMITED. Corpable does not collect them.