On this page
  1. Define the tracker boundary before adding columns
  2. Create a stable ID and identity block
  3. Separate reference price from the amount you authorize
  4. Use an event log instead of one overwritten status cell
  5. Make every open row answer who acts next
  6. Add warehouse fields only after intake
  7. Connect accepted items to a parcel group
  8. Use freshness rules and a weekly review
Private workflow, not a public databaseThe tracker follows products you selected and orders you actually placed. It should record decisions and status evidence without exposing account, address or payment details.

Define the tracker boundary before adding columns

A Superbuy personal order tracker is a private worksheet for one buyer’s selected products, purchases, warehouse items and parcels. Its job is continuity: it should tell you what was chosen, what happened next, which decision is open and which record proves the update. It is not a public Superbuy spreadsheet, product index or seller ranking. Those tools support discovery; this tracker begins after a candidate has entered your own decision process.

Keep the service paths separate. In the Shopping Agent flow, Superbuy purchases from a Chinese marketplace seller after you submit the item. Parcel Forwarding starts with an item you already purchased and send to a forwarding address. The two paths can use different fields, inspection expectations and support records. Add a service-type column at the start so a forwarding parcel is never treated as if the agent placed the seller order.

Use one workbook or table with linked views rather than unrelated notes. A simple design has three sheets: Items for the source and selected option, Events for dated status changes, and Parcels for international submission. Each row should connect through your own private item ID, not through a public title that can change.

  • Items: what you selected
  • Events: what changed and when
  • Parcels: how accepted items were grouped
  • Private ID: the link between all three

Create a stable ID and identity block

Assign a short private code as soon as a product becomes a serious candidate: for example, ORD-260828-01. The code remains stable when the seller changes the title, the platform shortens a translated name or several products have nearly identical descriptions. Do not use the row number as the only identifier, because sorting and inserting rows will change it.

The identity block should contain source URL, seller or shop when visible, neutral product name, product type, selected colour, size, model, version, quantity and intended included pieces. Preserve the exact option text as well as a readable note. A translated label such as ‘black upgraded’ may be ambiguous later; the original text or option image can help identify what the order meant.

Add a source-check date. The date does not guarantee the listing remained stable; it tells you when the captured identity was observed. If the source later redirects or changes materially, keep the original record and add a new freshness event instead of silently overwriting the decision history.

Separate reference price from the amount you authorize

Use different fields for spreadsheet reference, live option price, China domestic delivery, named order-stage services, displayed currency and authorized total. The reference amount explains why the item entered the shortlist. The live amount for the selected option supports the purchase decision. They should never be merged into one number because a headline price can belong to another option, an accessory or a deposit.

After payment, record the platform order amount and the payment-provider settlement in their original currencies. If your card issuer applies conversion or a foreign-transaction charge, keep that outside the platform-fee column unless Superbuy explicitly labels the same charge. A difference between two totals is a question to reconcile, not evidence of an invented markup.

Leave future international freight blank or mark it as a dated estimate. Superbuy’s public Shopping Agent guidance describes parcel submission and international payment after warehouse arrival. The later amount depends on destination, selected route, packing, weight and dimensions. Your item row should not pretend to know the final delivered cost before those inputs exist.

Use an event log instead of one overwritten status cell

A single status cell shows only the latest label and erases the path that produced it. Create one event row whenever a decision-relevant change occurs. Minimum fields are private item ID, timestamp, visible status text, event type, evidence reference, next owner and next review date. The next owner may be you, the purchasing agent, seller, Chinese carrier or warehouse.

Do not invent universal labels. Copy the wording from the live account and add your own normalized event type, such as submitted, buyer action required, purchasing, seller dispatched, domestic scan, delivered to warehouse, stored, accepted or return requested. The original text remains evidence; the normalized label makes sorting easier.

A seller tracking number and a carrier acceptance scan are different events. A domestic delivered scan and completed warehouse intake are also different. Recording those distinctions makes a support request precise. If a gap remains, you can provide order ID, tracking, last scan and exact missing handoff without relying on memory.

Make every open row answer who acts next

Add three action fields: next action, owner and review date. ‘Wait’ is acceptable only when it states what evidence will end the wait. For example: ‘Seller dispatch—review when first carrier scan appears’ or ‘Warehouse intake—review when stored item record is available.’ This turns the tracker from a diary into a control system.

When the account asks for an option or price decision, quote the request in the event log and record the response. Do not create a duplicate order simply because movement has paused. First check payment, unread messages, option confirmation and seller evidence. A duplicate can turn a tracking problem into two purchases.

Use a hold reason that is factual: missing buyer response, seller not dispatched, domestic tracking inactive, intake processing, QC question open or after-sales pending. Avoid emotional labels such as ‘scam’ or ‘lost’ unless evidence has established the condition. The tracker should help the next conversation, not prejudge it.

Add warehouse fields only after intake

When the item is stored, create a warehouse block with arrival date, warehouse item number, displayed intake weight, dimensions if shown, storage deadline in the live account, standard-photo review and decision. Intake data should not replace source identity. Reconcile seller, option, colour, size, model, quantity and pieces against the order row first.

Use three decision states: accept, clarify or after-sales. Accept means the visible evidence is sufficient for your threshold. Clarify means one targeted image, measurement or message could resolve a material question. After-sales means the available evidence documents a wrong option, missing part, damage or another mismatch that exceeds your rule.

Record ordinary QC status without turning the tracker into a QC tutorial. A field such as ‘standard photos reviewed—size label unresolved’ is enough. If a targeted request is made, link its result to the event log. Photos can support visible facts but cannot prove authenticity, composition, comfort, internal function or durability.

Connect accepted items to a parcel group

Create a parcel-group ID before submission and attach only accepted items. The group view should show product IDs, restrictions, packaging needs, approximate weight and reason for grouping. A fragile object, battery, liquid, rigid shoe box or unusually bulky textile may deserve a separate comparison because one item can change the routes available to the entire parcel.

Do not add item weights and call the sum the final billable parcel. Outer packaging, protection, consolidation and removal services can change both scale and volumetric weight. Record calculator inputs, dated estimate, selected route and deposit only when they exist. After packing, add verified weight, dimensions and final adjustment as later events.

Keep address and declaration records in a protected parcel area rather than repeating them across public-facing rows. The personal tracker can state ‘address checked’ and reference a private record. That preserves the audit without turning the worksheet into a sensitive identity file.

Use freshness rules and a weekly review

Choose a short review rhythm for open actions and a slower one for completed rows. At each review, filter by overdue next-review date, buyer action required, seller dispatch without scan, delivered without intake, warehouse items without a decision and accepted items without a parcel group. This creates a manageable queue rather than asking you to inspect every order every day.

Never delete a cancelled, refunded or returned item. Mark outcome, closing date and the linked transaction event. The closed row prevents the same source or option from being confused with a later repeat order. For repeat purchases, create a new item ID and recheck the live listing, because price, seller terms, option labels and availability may have changed.

A useful Superbuy order spreadsheet should answer six questions in seconds: what did I select, what amount did I approve, what is the latest evidence, who acts next, when will I review it and which parcel or outcome closed the row? If it cannot, remove decorative columns and improve those six fields before adding more detail.

  • Every open item has a next action
  • Every event has a date and evidence
  • Every warehouse item has a decision
  • Every accepted item has a parcel plan
  • Every closed item keeps its outcome
  • Sensitive data stays outside shared views
Browse product finds →Plan parcel weight →