Building a 1688 sourcing system when your shop is at 30 orders per day feels unnecessary. You know your SKUs, you know your suppliers, and you reorder when the shelf looks thin. That works fine until it stops working, usually somewhere around 80 orders per day, often suddenly.
The problem is not that you are bad at sourcing. The problem is that what you were doing was not a system. It was a set of habits that happened to be enough for the volume you had. Habits do not scale. Systems do.
This blueprint maps the sourcing problems you will hit at each growth stage (30, 80, 150 orders per day) and gives you a 5-layer framework you can start building in a Google Sheet today. No expensive software required to get started.
Why Sourcing Runs Fine at 30 Orders But Starts Breaking at 80
At 30 orders per day, a typical 1688 importing operation looks like this: you reorder when you notice stock getting low, supplier contacts live in Zalo chat (or your memory), and you track down the 1688 product link every time you need to place another batch. No spreadsheet, no reorder points, no fixed schedule.
This works because at small volume, margin and time absorb your mistakes. Miss a reorder by three days? You have buffer stock. Place the wrong quantity? You can move extra units eventually. The error cost is low enough that you do not feel it.
Around 80 orders per day, three things change.
The cost of a stockout becomes real. If your top SKU sells 40 units per day and you run out for three days, that is 120 lost sales, somewhere between 300,000 and 500,000 VND in missed revenue, sometimes more depending on your average order value. At 30 orders per day, a stockout was an inconvenience. At 80+, it is a measurable P&L hit.
You cannot hold the catalog in your head anymore. At 5 SKUs, mental tracking works. At 15-30 SKUs, you start mixing up variant codes, confusing supplier A's version of a product with supplier B's, and losing track of which shipment is pending from which source.
The link-lookup problem compounds. If finding the right 1688 URL, verifying the current price, and drafting a reorder message takes 20-30 minutes per SKU, that may be fine for 5 SKUs once a month. At 20 SKUs on different replenishment cycles, you are losing hours per week on a task that should take minutes.
This post is not a 1688 ordering tutorial for beginners. It is a blueprint for operators who are already buying from 1688 and need to structure what they are doing before the chaos of scaling buries them.
Three Growth Stages and the Sourcing Chaos That Comes With Each
The reason most operators hit a wall is not that they lack discipline. It is that they carry the same approach from one stage into the next, even when the new stage has fundamentally different problems.
Stage 1 (10-50 orders per day). You are running 1-5 core SKUs. Sourcing is mostly ad hoc, driven by gut feel. The main challenge at this stage is finding good suppliers and validating quality for the first time, not managing complexity. You probably do not need a formal system yet. You need good supplier relationships and one spreadsheet row per SKU.
Stage 2 (50-120 orders per day). The catalog has expanded to 10-30 SKUs. This is where things start going sideways. You mix up variant codes. You forget that SKU-07 came from supplier B, not supplier A. You miss a reorder because it was no one's specific job to check. You end up with three months of dead stock on SKU-12 while SKU-03 runs dry. The problem is not volume. It is that you are still sourcing like you did at Stage 1, just faster and with more SKUs.
Stage 3 (120-200 orders per day). You are now replenishing continuously from two or more suppliers. Daily inventory tracking is not optional. A single supplier going on holiday during Chinese New Year without warning can stop your entire operation. The coordination overhead is significant enough that it needs dedicated time and a real process, not just a chat thread.
Each stage needs different tools and different habits. Carrying Stage 1 habits into Stage 2 and Stage 3 is the single biggest cause of sourcing chaos when scaling.
The 5-Layer 1688 Sourcing System Blueprint
Here is the framework. Five layers, each solving a distinct failure mode.
- Layer 1: Standardized SKU catalog. Every SKU has a consistent record with an internal code, the 1688 link, last purchase price, MOQ, and supplier contact.
- Layer 2: Reorder points. Each SKU has a calculated quantity threshold that triggers a replenishment order, not a feeling.
- Layer 3: Fixed order schedule. Orders go out on a set calendar (Monday review, Tuesday order placement, Thursday follow-up), not reactively when stock runs low.
- Layer 4: Backup suppliers. Every high-velocity SKU has at least one vetted alternative supplier ready to activate.
- Layer 5: Inbound order tracking. Every purchase order has a record with the 1688 order ID, date placed, current status, and notes on any issues.
Think of it as five links in a chain. One loose link and the whole system has a failure point. If you have reorder points but no fixed schedule, you still have reactive sourcing with a number attached to it. If you have a schedule but no backup suppliers, one supplier going dark stops you cold.
Practical build order: start with Layers 1 and 2 before you think about any tool. Add Layers 3 and 4 as you reach Stage 2. Layer 5 only becomes painful to skip when you are running three or more concurrent inbound shipments.
This framework fits a team of 1-5 people. No ERP, no accounting software required to start.
Layer 1 and 2: Building Your SKU Catalog and Setting Reorder Points
The minimum viable SKU record has five fields: your own internal code (not the supplier's), the 1688 product URL, last purchase price, MOQ, and primary supplier contact.
Do not use product name as your identifier. Names drift. The 1688 URL is specific and clickable. If the listing disappears, you know immediately that something changed with that supplier or product.
Grouping SKUs by velocity lets you prioritize what to monitor closely. A simple three-tier breakdown works:
- Group A: selling 10+ units per day. Reorder weekly.
- Group B: selling 3-10 units per day. Reorder every two weeks.
- Group C: selling under 3 units per day. Monthly replenishment is fine.
If you want to get this data cleanly from your Shopee or TikTok Shop sales history, the calculations in our guide on 1688 inventory turnover rates walk through the exact math with worked examples.
The reorder point formula is straightforward:
Reorder Point = Average daily sales x Lead time in days x 1.25
The 1.25 is a 25% safety buffer for shipping delays and demand spikes. Concrete example: a SKU selling 30 units per day with an 8-day lead time from 1688 to your warehouse has a reorder point of 30 x 8 x 1.25 = 300 units. When stock hits 300, you place the order. Not when it hits 100 and you start to panic.
Build this formula into your Sheet for every SKU. Update lead time if your supplier's shipping changes. Update average daily sales each month.
Monthly catalog maintenance takes 30 minutes if you do it regularly: remove any SKU that has not sold in 60 days, update the last purchase price from your most recent order, confirm the 1688 link is still live, and verify your supplier is still active. Skip this for three months and you are making decisions on stale data.
Layer 3, 4, and 5: Fixed Order Cycles, Backup Suppliers, and Order Tracking
A fixed order schedule solves the reactive sourcing problem. Instead of placing orders when you notice stock is low (which is already too late for Group A SKUs), you set a weekly rhythm: Monday is inventory review, Tuesday is order placement on 1688, Thursday is shipment status check.
This matters beyond your own operations. When suppliers see a consistent ordering pattern from you, they process your orders with fewer errors. You become a predictable buyer, which usually means better responsiveness and sometimes better pricing over time.
Why you need at least two suppliers for every Group A SKU: any supplier can go out of stock without warning, raise prices overnight, or go quiet during a Chinese public holiday. If your top SKU is single-sourced and that supplier has a problem, you have no option but to stop selling or scramble on 1688 under pressure. That scramble costs 3-5 days minimum and usually means paying a premium. Having a vetted backup means you activate them with one message, not a crisis. For how to structure supplier relationships so you are not dependent on any single source, the post on building a 1688 supply chain without single-supplier dependency covers the vetting and negotiation side in detail.
Vetting a backup supplier on 1688 before you need them: check their overall rating and average chat response time, place a test order of 5-10 units, and compare actual product quality against listing photos. If quality matches and they ship within their stated lead time, add them to your catalog as the secondary source. For a structured quality check process, see our guide on verifying 1688 product quality before payment.
Layer 5 can be four columns in a second spreadsheet tab: 1688 order ID, date placed, status (ordered / in transit / received), and notes. That is enough to prevent the two most common inbound tracking failures: forgetting an order exists and mixing up which shipment belongs to which supplier. When you are running three concurrent inbound shipments from different sources, this tab earns its existence every single week.
Tools for Each Stage: From Spreadsheet to Semi-Automated
Stage 1 (under 50 orders per day). A six-column Google Sheet is genuinely sufficient. SKU name, 1688 link, current stock, reorder point, last order date, supplier note. Nothing else. Do not buy software at this stage.
Stage 2 (50-120 orders per day). Add a second tab for inbound order tracking. A Notion database with linked supplier records also works well here if your team is already in Notion, since you can manage pipelines from multiple suppliers simultaneously without confusing shipment batches.
Stage 3 (120-200 orders per day). At this volume, manual stock entry becomes the bottleneck. You need a way to pull inventory data from Shopee or TikTok Shop automatically so your reorder calculations use real-time numbers, not last Thursday's manual count. This is when sourcing-specific tooling starts paying back its cost in time saved and stockouts prevented.
The most important principle across all three stages: do not invest in more complex tooling until your process is stable. A tool built on a broken process just fails faster, with better-looking dashboards. The best tool is the one your team actually uses every day, not the one with the most features.
Common Mistakes When Scaling Your 1688 Sourcing Operation
Bulk buying for discount tiers. Ordering six months of stock to hit a 15% price break sounds logical until you realize you have tied up capital for 60-90 days on one SKU while other SKUs run out. If your product has any seasonality or trend sensitivity, the risk is worse. The full cost-of-goods calculation for 1688 imports shows how to model this properly before committing to large quantities.
Missing costs in your landed price. Domestic shipping within China from the factory to a consolidation warehouse, border crossing fees, and intermediate warehouse handling are frequently omitted from unit cost calculations. If your cost basis is wrong, your selling price is wrong, and you may not discover this until you run the numbers three months later. Our breakdown of 1688 import fee structures covers each cost layer.
Tracking stock by memory at 20+ SKUs. No one can hold accurate inventory counts for 20+ SKUs in their head simultaneously. The failure mode is predictable: either you double-order (wasting cash) or you go stockout (losing revenue). Both happen regularly to operators who scale their SKU count without scaling their tracking.
No backup for your top SKU. Every operator who has been doing this for more than 12 months has a story about their main supplier going dark. If you have not built a backup yet, the question is not whether this happens to you, it is when.
Expanding SKU count before your process is stable. Adding 10 new SKUs while your existing 15 are already poorly tracked means you end up with 25 SKUs managed badly. The chaos compounds with each addition. Get your existing catalog clean and running on a real reorder system before you expand.
FAQ: Building a 1688 Sourcing System as Your Shop Scales
At what order volume should I start building a formal system?
Most operators can manage informally up to about 40-50 orders per day if they have 5 or fewer core SKUs. Above 50 orders per day, or above 10 active SKUs, building Layers 1 and 2 now will save you time this week, not just next month.
What is the minimum information I need to record per SKU?
Internal code, 1688 product URL, last purchase price, MOQ, and primary supplier contact. That five-field record eliminates the link-lookup and price-recall problems immediately. Add the reorder point formula once you have two weeks of sales data.
Should my order cycle be weekly or monthly?
For Group A SKUs (10+ units per day), weekly ordering is safer. For Group B (3-10 units per day), bi-weekly. Monthly replenishment is only appropriate for slow-moving items. If your 1688 lead time is under 10 days, you have a little more flexibility on cycle length, but the fixed schedule still matters more than the frequency.
How do I make the reorder point formula more accurate?
The basic formula is a starting point. Make it more accurate by tracking your actual lead time per supplier rather than using a generic estimate, and by raising the safety multiplier from 1.25 to 1.4 if your demand has high variance week-over-week or if your supplier's on-time rate is below 80%.
What does Ordinex Scout handle that a spreadsheet cannot?
Scout is built for Stage 3 operators sourcing across multiple suppliers concurrently who need inventory figures to stay current without manual entry. It connects to sales channel data to keep reorder calculations updated automatically and tracks inbound order status in one place, replacing the combination of chat threads, separate tracking sheets, and manual cross-referencing that most Stage 3 operators are living with.
If you are currently at 50-80 orders per day and sourcing still feels ad hoc, Layers 1 and 2 are worth building this week. A few hours of setup and the reorder point formula alone will prevent your next stockout. If you are approaching 120+ orders per day and want early access to Scout (currently in private beta), you can register at ordinex.cc.