Publish Time: 2026-09-21 Origin: Site
After-sales is the work that starts after the carton arrives: a wrong line, a short line, a unit that will not work, or a part that will not fit. You can run that work in two ways, and they are not interchangeable.
Per-supplier handling puts the next case on the queue of the desk that shipped that unit. Each vendor keeps its own list. Centralised tracking puts those cases on one shared file, so you can see whether a case has a number, how long it has sat, and whether the same fault has already come back.
Ranking two quotes by the unit price printed first on the PDF — the first line — has not compared those jobs. A cheaper unit price has not named which job you needed. A sheet that invents a house supplier-count switch number has not named it either. This house will not publish that number.
The missing question is where the next ticket lives. A ticket here is one after-sales case. Either it still sits on one supplier’s queue, or it sits on one shared file as desks and tickets both grow. Those two homes are the comparison.
Cheap per-supplier handling can still leave history unread: you have names to call, not a record of what already failed. Paying more for a shared file can still be the honest cost of watching that history. Rank two sellers by unit price, and that scale goal stays off the sheet.
Order size on the parts invoice does not close the gap. Stacking a larger mixed parts buy — more than one model packed together — still leaves several queues as several queues. Shrinking the buy does not turn a shared file into a per-supplier queue. How you score a sample against a small-batch trial is a different article. This split is narrower: read after-sales as two tracking jobs, or score the cheaper PDF and leave the job unread.
Ask, on the quote, whether the next ticket should sit on that supplier’s queue, or on one shared file. Cutting the unit price still leaves that ask blank. Extra words on a cheaper quote describe the shape of that quote. They are not this split.
It puts the after-sales queue on the desk that shipped that unit. That is the point of the model: the next ticket still sits on that shipping desk. While each of those desks can still own the next case, talking to each queue can still be acceptable coordination.
The same buy leaves shared history unread once many desks are in play. A contact list — a name and a number for each vendor — is not a tracking sheet. It does not give a case an identifier, and it does not show whether the same fault has already come back.
Netfor published a 2 April 2026 note on the cost of many vendors, read here on 9 September 2026. That page is useful for one warning: as the vendor list lengthens, leaving every name on its own queue raises coordination cost. The application-count and downtime stories stay on that page. They are not a MILDTRANS supplier-count table.
A quote that treats a cheaper first line as proof the next ticket will have a home has not answered the job. No dated page found here names a MILDTRANS count that forces a shared file. A per-supplier queue belongs where the next ticket can still sit on that supplier’s queue. Stopping at contacts leaves a shared-file need unread.
It opens one file for tickets that used to live in separate inboxes. That is the point of the model: one identifier, one place to see handling time, and one place to see whether the same fault has already come back. If cases never share a file, repeats stay hidden.
The unread cost is treating that file as “just more email.” A shared inbox with no identifier is still several queues wearing one label.
ERP Implementation’s 2026 after-sales note, read the same day as the Netfor page, is useful for one warning: if cases never share a file, you cannot see whether the same fault has already come back. The hours-per-case stories on that page stay there. They are not this desk’s ticket clock.
A central file that only exists as a cheaper first line is not a plan. Check whether this list still needed that supplier’s queue, or a shared file.
Per-supplier handling still fits while each shipping desk can own the next case. Centralised tracking fits once desks and ticket frequency both grow. One tracking sheet then cuts the coordination that a lengthening vendor list creates. The two sheets do not replace each other. Unit price on the PDF does not name which sheet you needed.
A desk list that has not yet forced a shared file does not need one stacked on top of it. History is unread if you stop at contacts once desks and tickets both grow.
Chasing the cheapest per-supplier queue on every name looks careful and usually is not, because history still sits unread. Chasing the cheapest shared file looks thorough and repeats a queue you did not yet need to leave. Netfor and the 2026 after-sales note already name that vendor-count versus one-file split. They do not fill this confirmation, and they do not hand this house a switch number.
Write the list in two columns before you rank sellers. Column one is the tickets that can still sit on one supplier’s queue. Column two is the tickets that needed a shared file. Until those two columns exist, a cheaper first line has not compared centralised tracking with per-supplier handling.
After-sales here already runs as one window rather than a queue per supplier. Wrong shipment, short shipment, quality, and compatibility sit on that window, and restock, return, or a price difference can follow when needed. That is a centralised tracking sheet on this desk. Buyers will not find a published count that says when to leave each desk’s queue.
Dead-on-arrival cover — DOA, a unit that does not work when it arrives — is 30 calendar days from signed receipt. Calendar days count every day, including weekends. Both a photo and a video are required. Screens here are covered for 3–12 months; batteries and adapters for 12 months.
A first look is due in 2 working days after complete papers. Working days skip weekends; they are not the same count as calendar days. Confirmed DOA is replaced, reshipped, or refunded in 3–5 working days after that confirm. Count those days as after-sales clocks. Do not count outbound 7–15 days as the wait for a ticket to find a home. That window is how a confirmed mixed line leaves, not how a case is opened. Leaving the same calendar day is not how this desk usually ships.
Shenzhen Mildtrans Industrial Co., Ltd. (深圳市中川实业有限公司) dates from 2004, and Mildtrans Industrial Co., Limited (中川实业投资有限公司) dates from 2010 in Hong Kong SAR, China. Most invoices use the Hong Kong name. The desk purchases parts and sends mixed lines out. It is not a factory. Money moves as T/T — telegraphic transfer, a bank wire — through HSBC. A letter of credit — a bank-guaranteed form of payment — is refused.
A per-supplier sheet and a centralised sheet are not the same kind of paper. The table below is the check on the quote. If a seller will only quote a lower unit price, leave this comparison unread. A complete sheet names which tickets still live on one desk, and which needed a shared file. A higher first line does not become that sheet because the unit price is higher.
Question | Per-supplier sheet | Centralised sheet | Netfor / ERP 2026 note (read 9 Sep 2026) | Stop |
What is named? | One queue per shipping desk | One shared file | Oversight in one place versus each vendor’s queue | First line treated as the split |
Does a lower unit price write the split? | No: still write queue versus shared file | No: write queue versus shared file | Those notes name queues versus one file, not a cheaper PDF | Cheap PDF treated as a tracking check |
Does ticket history get recorded? | Often unread once desks multiply | Yes: one identifier, one file | Without one file, repeats stay hidden | Contacts treated as history |
Does outbound 7–15 days write an after-sales clock? | Leave unread | No: that clock is dispatch | Those notes time tickets on the file, not on a dispatch window | 7–15 treated as a ticket wait |
Is a house supplier-count switch on the sheet? | Leave unread | Leave unread; write the two columns | Vendor counts stay on their pages | Vendor start treated as house |
· This desk tracks after-sales on one window.
· Screens are covered for 3–12 months; batteries and adapters for 12 months.
· DOA is 30 calendar days from signed receipt; a photo and a video are both required.
· Netfor (2 April 2026) and the 2026 after-sales note were read on 9 September 2026.
· No house figure names how many names force a shared file.
Leave that quote unread for this comparison. Ask which tickets still live on one desk, and which needed a shared file. A price cut does not create a history check, and a higher first line does not create a per-supplier queue. Until those two columns are named, treat a quote that only repeats a cheaper first line as unfinished. Treat an invented supplier-count switch the same way: unfinished, until the seller writes the goal.
The questions below keep the same check: write queue versus shared file, then rank. A dispatch window is not an after-sales clock. A cheaper first line is not a tracking sheet either. Until each ticket is marked as per-supplier or centralised, treat the two PDFs as unfinished for this split.
How do you compare centralised after-sales tracking with per-supplier handling as you scale?
Stop before the lower first line. Mark which tickets can still sit on one supplier’s queue. Mark which tickets needed a shared file. Until that split sits on the sheet, the two first lines are not the same kind of figure.
Is per-supplier handling always the wrong choice?
Not if the next case can still sit on that supplier’s queue. The unread risk is treating a contact list as proof the next ticket will still have a home once desks multiply. Judge the list by what home the next ticket must have, not by the cheaper first line.
Does a shared file mean I should skip the shipping desk’s queue?
No. Keep the supplier’s queue when the next ticket can still sit there. Open a shared file when desks and tickets both grew. A file that repeats a queue you did not yet need to leave is usually the wrong choice.
Do MILDTRANS outbound days replace after-sales tracking?
No. The 7–15 day window named on this desk is how a confirmed mixed line leaves, not how a ticket finds a home. After-sales here already runs as one window. The desk has not named a count that forces a shared file.
Is a vendor’s published supplier-count switch this house’s policy?
No. Dated public notes may show vendor-count stories. Those figures stay on those pages. Split by queue versus shared file. Fill the two columns. A vendor count on those pages is not this desk’s switch.
Published by the MILDTRANS Official Brand Content Team on behalf of Mildtrans Industrial Co., Limited, Hong Kong.