Harbolnas seller preparation is the difference between the two stories I hear every December. Story one: "11.11 was our best day ever, and 12.12 topped it." Story two: "We did huge volume, then spent January processing refunds, chasing lost shipments, and realizing we barely made money." Same traffic spike, same platforms, completely different outcomes.
With 11.11 nine days away and 12.12 following, this is the last realistic window to prepare properly. The marketing side, banners, vouchers, flash-sale slots, gets plenty of attention from the platforms themselves. What kills sellers is everything the platforms do not remind you about: margin math, stock allocation, customer-service load, and the systems underneath it all.
Here is the preparation checklist I walk sellers through, in order of how expensive each mistake is.
Do the Margin Math Before You Set a Single Discount
The most expensive Harbolnas mistake happens in a spreadsheet weeks before the event: setting discounts by feel. A 40 percent discount does not cost you 40 percent of profit. It usually costs far more, because your margin is a fraction of your price.
Work through one product honestly:
| Line | Normal | 11.11 at 40% off |
|---|---|---|
| Selling price | Rp 200,000 | Rp 120,000 |
| Product cost | Rp 110,000 | Rp 110,000 |
| Platform fees and program costs (approx 8%) | Rp 16,000 | Rp 9,600 |
| Packaging and handling | Rp 6,000 | Rp 6,000 |
| Margin per unit | Rp 68,000 | fewer than Rp 0 |
That product loses money on every unit at 40 percent off, before ads and before a single return. Sometimes a loss-making hero deal is a deliberate customer-acquisition play, and that is fine, if it is deliberate and capped in quantity. The disaster version is discovering it in January.
The practical move: build a one-line margin calculation for every SKU in the campaign, decide the maximum defensible discount per SKU, and pick 2 or 3 loss-leader deals with hard stock caps. Deep discounts on the traffic magnets, healthy margins on everything the traffic buys alongside them.
Allocate Stock Across Channels, In Writing
If you sell on more than one channel, marketplace stores, your own site, WhatsApp resellers, offline, campaign day is when overselling happens. Two channels sell the same last 50 units, and now you are cancelling paid orders, which costs you penalty points on the platform and trust with customers.
Before 11.11:
- Split stock explicitly per channel and write the allocation down. If your systems do not sync inventory in real time, do not rely on mental math during a spike.
- Hold a reserve of 5 to 10 percent for replacements of damaged or lost shipments. Sending a replacement in 2 days beats a refund fight in every case.
- Decide the out-of-stock behavior now. Which SKU goes dark first, whether you redirect to a substitute, who has authority to pull a listing mid-campaign.
Overselling is not a marketing failure. It is an operations failure that erases whatever the marketing achieved.
Plan Customer Service Like a Shift Manager, Not an Optimist
Chat volume on campaign days runs 3 to 8 times normal, and response speed directly affects conversion, because a bargain hunter with a question buys from whoever answers first. It also affects your ratings when things go wrong afterward.
Minimum sensible preparation:
- Templates for the top 10 questions. Shipping estimates, size or variant questions, voucher stacking rules, COD availability, warranty. Write them this week, in a tone that sounds like your store, and put them where every CS person can paste them.
- Scheduled coverage for the spike windows. Midnight to 2 am on the day itself, lunch hour, and 8 to 11 pm. Assign names to hours. "Everyone helps out" means nobody is accountable.
- An escalation rule. Complaints and cancellation requests go to one senior person. Junior staff improvising refund promises at 1 am creates commitments you cannot honor.
If you have wondered whether automation could absorb some of this load, the honest cost breakdown in Chatbots vs Live Agents: The Real Cost Comparison applies double during campaign season: automate the repetitive 60 percent, keep humans on everything involving money and anger.
Check the Systems That Only Break Under Load
Harbolnas seller preparation has a technical layer that sellers on marketplaces mostly inherit from the platform. But if you run your own store or landing pages, the traffic spike is yours to survive.
- Load-test the checkout path, not the homepage. A product page that renders slowly loses some sales; a checkout that times out loses all of them.
- Verify payment webhooks and order notifications. During spikes, delayed payment confirmations generate a flood of "sudah bayar tapi status belum berubah" chats that will bury your CS team.
- Test the promo logic with stacked vouchers. Discount rules interact in ways nobody predicted, and a miscoded voucher that makes orders nearly free will be discovered and exploited within minutes on campaign night.
- Know your rollback plan. If a promo misfires, who can disable it, and how fast, at 00:15 on 11.11?
One seller I advised found during a dry run that their stock-deduction logic had a race condition: two simultaneous checkouts of the last unit both succeeded. Trivial to fix in October, a public apology in November.
Plan the Follow-Up Before the Campaign, Not After
Most sellers treat Harbolnas buyers as one-off bargain hunters, and if you do nothing, that is exactly what they become. But you are paying, in discounts and fees, to acquire thousands of customers in 48 hours. The follow-up is where that spend turns into an asset.
Prepare in advance: a thank-you message with a modest voucher valid in the quiet weeks between 11.11 and 12.12, a gentle review request 3 days after delivery, and proper tagging of campaign buyers so you can see, in March, whether any of them came back. That last part is a data habit that pays off well beyond the campaign, in the way I described in Dark Data: The Answers Already Buried in Your Business.
The Practical Takeaway
Nine days is enough if you sequence it: margin math and discount caps first, then stock allocation, then CS templates and shift schedule, then system checks, then the follow-up messages, all before 10.11. Whatever ships on 11.11 becomes your dress rehearsal report for 12.12, so keep notes on what broke.
Harbolnas rewards the prepared and punishes the improvised, at scale, on a deadline that does not move. Spend this week on the boring parts and let December be story one.