Black Friday and Cyber Monday can bring five to ten times normal traffic in a single weekend. This is a checklist for getting a store ready for the peak, from stock levels through invoices and carriers to the order monitoring that stops anything disappearing in the rush.
Black Friday and Cyber Monday are the strongest weekend of the year for most stores. Traffic can grow five to ten times over a normal day, and orders arrive from Allegro, eBay, Erli and your own WooCommerce or Shopify store all at once. The catch is that the size of the discount does not decide whether you make money at peak. Whether your operations can carry it does.
The most common Black Friday failures have nothing to do with marketing. They are goods sold that were not in stock, invoices issued three days late, parcels that missed their despatch, and orders that quietly got stuck between systems. Each of those escalates exactly when the largest number of customers is watching how you perform.
So treat Black Friday preparation as an operational audit, not a promotional campaign. Below is a checklist area by area, from the warehouse through invoicing and despatch to monitoring, with concrete steps to tick off.
A short calculation to show the scale. A store that normally does 40 orders a day at an average value of 180 PLN turns over roughly 7,200 PLN daily. If Black Friday multiplies volume by seven, over 280 orders and something near 50,000 PLN pass through the store in one day. Any process that takes a minute of manual work at 40 orders grows to nearly five hours at 280. You will not make that up with extra hands on Saturday, you have to remove it with automation beforehand.
At peak, overselling is risk number one. The same bestseller sells from three channels within minutes, and if stock updates lag you will sell goods you physically no longer have. The result is cancelled orders, worse marketplace ratings and, on Allegro, a real risk of penalties for unfulfilled listings.
The foundation is keeping stock in step across every channel in close to real time. NavyFlame updates stock between platforms, so a sale on Allegro immediately removes a unit from availability in your store and on eBay. The feature itself lives in the warehouse management module.
Extra protection is worth adding for the peak. A checklist:
After Black Friday you return to normal buffers. The whole point is to hold a margin of error through the 72 busiest hours, not to manage every unit by hand.
Remember multi-channel selling too. If the same product is listed on Allegro, in your WooCommerce store and on Erli, each channel drains stock at its own pace. Without a shared stock level you risk three platforms selling the same last unit in the same minute. A central warehouse solves that at the source: there is one level, and the channels only read availability from it.
Invoicing is manageable by hand at normal volume, and the first thing to break at peak. If you normally issue 30 invoices a day and Black Friday brings 300, retyping buyer details, tax numbers and line items guarantees delays and errors. A mistake in a VAT rate or a tax number at that volume can spread across dozens of documents before you catch it.
The answer is issuing invoices automatically the moment an order is paid. NavyFlame ties marketplace and store orders to accounting systems (wFirma, inFakt, Fakturownia, iFirma) and issues the document with the correct buyer details, tax number and VAT rate, ready for KSeF. The whole flow from order to invoice is described on the orders to invoices automation page.
What to tick off before the weekend:
Automating invoices is not only about saving time. It is also the peace of mind that ten times the volume will not land you with VAT errors born of haste.
The best promotion will not help if the parcels do not leave on time. After Black Friday customers expect their order to move within a day or two, and delays generate waves of messages and bad reviews. Despatch is the most physical bottleneck of the peak: packing time, label availability and carrier throughput all count.
Generate labels automatically instead of typing details into the carrier's panel. NavyFlame integrates InPost, DHL and Poczta Polska, picks the carrier by your shipping rules and collects the tracking number that goes back to the marketplace. You will find the rule configuration in the shipping automation module.
A despatch readiness checklist:
The point is that on Saturday morning your packers should not be generating labels one at a time. A label ready on the order cuts handling from minutes to seconds, and across several hundred orders that is a difference of hours.
At normal traffic a single error is easy to spot. At peak, with orders arriving in the hundreds, an error vanishes, and you find out when a customer asks where their parcel or invoice is. That is the most insidious part of a sales peak, because the loss stays invisible until the complaint.
So you need two things: a real-time view of orders and a mechanism that catches whatever failed. NavyFlame provides order monitoring with a dead letter queue. When an operation fails, a carrier rejects an address, an accounting system briefly stops answering, a field is missing, the order lands in the error queue instead of quietly vanishing. You see the cause and retry with one click once it is resolved.
What to set up for the peak:
The point of monitoring at peak is simple: instead of firefighting after complaints, you put fires out as they start, while the customer has noticed nothing.
More sales also means more questions. Customers ask about availability, parcel status, address changes and returns. It is worth preparing a set of ready answers and stating realistic despatch dates plainly, because a broken promise hurts more than an honestly longer wait. Order status and despatch notifications take a large share of those questions away before the customer even writes.
Post-Black-Friday returns are their own subject. Higher sales volume means more returns, and each one means a correction invoice and a unit going back into stock. Prepare a simple, repeatable path: accept the return, correct the invoice in the accounting system, update the warehouse. The fewer manual steps, the fewer mistakes in December.
Finally, pricing and promotions. The pricing decision is yours, because NavyFlame has no automatic repricer and no AI picking discounts. What you get is sales data and reports (channels, countries, bestsellers) to judge what is worth discounting and at what margin. You apply the promotional prices to channels through catalogue export and listing updates, so you are not clicking every listing on every platform.
Putting it together, the full Black Friday checklist looks like this:
| Area | What to tick off | Where in NavyFlame |
|---|---|---|
| Warehouse | Stock sync, buffers on bestsellers, verified deliveries | Features: warehouse |
| Invoicing | Rehearsed path, B2B and B2C rules, unbroken numbering | Orders to invoices automation |
| Despatch | Volume declared to carrier, rules, label test, materials | Shipping automation |
| Monitoring | Duty roster, e-mail alerts, error queue review | Features: monitoring |
| Service and pricing | Ready answers, returns path, pricing decisions from reports | Reports and catalogue export |
A well-prepared peak is not about heroic catching-up at three in the morning on Saturday. It is about operations, stock, invoices, labels and monitoring, running themselves, so you handle the exceptions rather than every individual order.
A realistic start is four to six weeks before the last Friday in November. In that window you verify stock levels, set safety buffers, test invoice and label automation, and agree volumes with your carriers. Leave the final week for end-to-end rehearsals and a change freeze: never roll out a new integration the day before the peak.
The usual cause of overselling is stock syncing between channels too slowly. At peak the same product sells from Allegro, your store and eBay within minutes. NavyFlame keeps stock in step between channels in close to real time, and an extra safety buffer on bestsellers (two or three units in reserve) protects you from selling goods that are already gone.
At ten times the volume, issuing invoices by hand is the first thing to break: delays grow, tax numbers get mistyped and VAT rates go wrong. Automatic invoicing issues the document with the buyer's details the moment an order is paid, whatever the hourly volume. That takes the most tedious part of the peak off the seller.
The odd error is unavoidable at peak: a carrier rejects an address, an accounting system briefly stops answering. A dead letter queue catches those orders instead of losing them, shows the cause, and lets you retry with one click once the problem is fixed. No paid order falls out of the process.
Tell your carrier the expected volume ahead of time, check despatch limits and collection hours, and generate labels automatically from shipping rules rather than by hand. It is worth rehearsing the whole path from order to finished label on a few test orders, so you do not discover missing despatch data at the peak.
You set promotional prices on the individual channels, and NavyFlame helps push them out through catalogue export and listing updates on marketplaces. There is no automatic repricer here and no AI picking prices: the pricing decision is yours, and the system speeds up applying it across several platforms.
A backorder is a sale of a product you temporarily do not hold, fulfilled once stock returns. How to introduce it safely, how it differs from a preorder, and how to avoid overselling.
A comparison of the Amazon FBA and FBM logistics models: costs, control, requirements, and how to manage orders and invoices whichever fulfilment method you choose.
How the B2B, B2C and D2C models differ. Invoices, tax numbers, pricing, deferred payment terms, and how to run several sales models at once.
See the full interactive demo with no sign-up, and watch how NavyFlame holds operations together at peak.
See the demoWe use cookies to keep the site working, to measure traffic and to personalise content. Read more in our privacy policy.
Manage preferences
