Company news, industry insights and cross-border knowledge — updated regularly.
RSSInsurance is not a must-buy; it depends on your goods' value density and the cost of a return. Here is when it is worth it, which clauses to read, and a table by value band.
Read moreInventory mismatches are not accidents — they come from an undefined counting method and an unclear sync direction. Here is the daily order: who moves stock, how to count, how to handle variance, with a cause-and-action table.
Read moreA damage claim lives or dies on the photos you took before dispatch. Here is the timeline: evidence before dispatch, how to open and inspect, how to photograph, and what to do when evidence is thin.
Read moreHandling multiple platforms is not hard on the order intake side — it is hard on shared inventory, status callbacks, and split returns. Here is the implementation order, with a table of where platforms differ.
Read moreHealth products are not general goods in a personal parcel. Here is the order to confirm things in: identify the format, ask about channel limits, then declaration and packing, with a table by common dosage form.
Read moreA return address is not one field. Set wrong, it sends returns to a platform hub, the wrong country, or an address nobody signs for. Here is the order: address ownership, who declares, who pays.
Read moreA transit number is not a promise, it is a range. Here is how to break it down: which legs make it up, which one is most likely to stretch, and how to ask for a figure that means something.
Read moreVocabulary problems become question problems. Here are the terms grouped by the situation you meet them in — charging, declaration, clearance, and channels — with a table and notes on which ones get confused.
Read moreComparing prices is the easiest step to get wrong. Here is the real screening order: can they take your categories, how is it charged, what is the compensation, the transit, and the self-service tooling.
Read moreA product name that is too vague gets a request for more detail; one that is too specific may trigger regulatory conditions. Here is the order: pick the granularity, align the required elements, then check the foreign-language version.
Read morePeak-season problems are rarely caused by warehouse capacity. They come from incomplete data, unsynced stock, and channels that were not enabled. Here is the pre-dispatch order: data, stock, channels, paperwork.
Read more