The last date you can promise delivery before Christmas

December’s temptation is obvious: the demand is there, the buyer is willing to pay, and every extra day you leave a listing active means more sales. So the easy decision is to keep selling through the 23rd and sort it out later. The problem is that a gift order is not fulfilled when you deliver it: it is fulfilled when it arrives before the date the customer needed it. After that it is not a late delivery, it is a useless purchase, and the buyer treats it exactly that way.

That is the asymmetry almost nobody quantifies. A sale you did not make costs you that unit’s margin. A sale you promised and failed to deliver on time costs you the return, the outbound shipping, sometimes the return leg too, the negative rating, the claim, the hit to a reputation score that drags for weeks, and the risk that the marketplace starts showing you less in the most expensive month of the year to lose exposure. These are not the same size. Not close.

That is why the most profitable operational decision in the second half of December is not how much to discount: it is the day you stop promising. And the marketplace does not hand you that day: you compute it, with your real handling time, the carrier you actually use and the geography you actually ship to.

This post is about how that date gets calculated, which variables move it, and what to do with your listings in the days that remain.

the delivery promise is a calculation, not a policy

When a buyer sees “arrives December 22” on your listing, they are seeing the result of a sum with three parts.

• Handling time. The hours or days between the order landing and you handing the package to the carrier with a label generated. This is entirely yours.
• Transit time. What the carrier takes from your drop-off point to the buyer’s address. Depends on the service level and the destination.
• Non-working days. Weekends, December 12, the 25th, January 1, and the days when the carrier runs reduced hours or does not pick up.

If the product sits in FBA or in Full, the first component is not yours: the marketplace network runs it, and the date shown comes from their own calculation. If the product ships from your warehouse, the first component is your decision and it is also the one that breaks most easily in peak season, because volume climbs and your packing capacity does not.

The key point is that the sum is not an average: it is a commitment. And commitments get sized with the reasonable worst case, not the typical case.

how to compute your promise cutoff

Start from the date the buyer has in their head and subtract backwards. For a delivery that has to be in the customer’s hands on Wednesday, December 23, with example numbers you should replace with your own:

• Delivery to customer: Wednesday the 23rd.
• Transit to a metro destination, ground service: 3 business days → hand to the carrier by Thursday the 17th.
• Your real peak-season handling time, not your March one: 2 days → the order has to land by Tuesday the 15th.
• Buffer for one failed delivery attempt: 1 day → Monday the 14th.

With those assumptions, your last safe date to promise a pre-Christmas delivery to that zone is Monday, December 14, not the 20th. Six days separate the real calculation from the gut feel, and every January claim fits inside those six days.

Now run the same exercise for a destination outside a metro area. If ground transit to that postal code is 6 business days instead of 3, your cutoff moves to Wednesday the 9th. And if the SKU has to travel from your warehouse to a fulfillment center before it ships to the customer, you add that leg too.

Which leads to the uncomfortable conclusion: you do not have one cutoff date, you have several, one per combination of delivery zone and shipping service. Treating them as one, using the most optimistic number, is the standard way to break the promise.

Glossary: lead time, the real end-to-end clock →

handling time is the first thing that breaks

If you self-fulfill, the component that degrades most in December is yours, and it is the least watched because it is never a problem during the rest of the year.

The mechanics are simple. If you normally process 25 orders a day with one person packing, and in the second week of December 90 a day come in, your one-day handling time becomes three without anyone deciding that it should become three. They pile up on the table. And because the promise you published still says one day, every incoming order is born late.

Three things that actually move that number:

• Measure it, do not assume it. Real handling time is the median hours between the order timestamp and the moment the label is marked as handed to the carrier. If you do not have it measured, start this week: two weeks of data beats any estimate.
• Adjust the published promise before it breaks, not after. Raising handling time from one to two days costs you some conversion. Breaking the promise costs you reputation. The first is a cost you choose; the second is a cost you get charged.
• Separate peak capacity from normal capacity. If your season plan does not say who packs on Saturday the 19th, your handling time for Monday the 21st is already decided.

what you control and what you do not

Worth being explicit, because December’s frustration comes from confusing the two lists.

You control: handling time, which shipping service you offer per zone, which zones you accept, the date you stop promising pre-Christmas delivery, which SKUs stay active and with how much stock, and the message you give the buyer before they purchase.

You do not control: the carrier’s real transit, the weather, delivery-network congestion, failed delivery attempts, or how the marketplace chooses to display the estimated date.

The practical consequence is that your buffer has to live on the side you control. You cannot make the carrier faster, but you can stop promising three days earlier. You cannot prevent a failed attempt, but you can count it in the calculation.

what over-promising costs: the arithmetic

Let us run an example, because the argument only lands when it shows up in money.

Take a product selling at 890 pesos with a net margin of 180 pesos per unit after commission, shipping and COGS. You decide to leave the listing active five extra days promising pre-Christmas delivery, and in those five days you sell 40 additional units.

The optimistic scenario: they all arrive. You made 7,200 pesos of margin.

The realistic scenario: 30% arrive after the 24th. That is 12 units. Of those, say 9 get returned. Each return costs you the outbound shipping you already paid, the return leg, reconditioning if it comes back opened, and the margin that never materialized. If that adds up to 320 pesos per returned unit, that is 2,880 pesos. The 28 that arrived fine leave 5,040 of margin. You are up 2,160 pesos.

But the part that never shows up on the sheet is missing: 12 buyers with a bad experience in the month with the most ratings, several claims opened inside the window that measures your reputation, and the effect of that on your exposure in January and February. If the reputation hit costs you even 5% of visibility for two months, those 2,160 pesos become the worst decision of the quarter.

The arithmetic is illustrative and the figures are examples. What is not an example is the shape of the curve: the extra margin is linear and capped, the reputation damage compounds and drags.

how Amazon and MercadoLibre measure it

Both marketplaces turn promise compliance into a metric of yours, and in both cases it is worth understanding the mechanics before deciding how much to risk.

On Amazon, the direct indicator for orders you fulfill yourself is the late shipment rate, which measures what share of your orders you ship-confirmed after the committed date. The third-party material we checked puts the limit at under 4%, and valid tracking rate above 95%, both over 30-day windows. Those numbers get repeated a lot, but Amazon’s public documentation defines the metric without always confirming the live threshold per marketplace, so confirm it in the Account Health section of Seller Central, which is where the target that applies to you is shown. Order defects are covered separately in Order Defect Rate and account health.

On MercadoLibre, reputation is calculated over a rolling 60-day window and built from three factors: claims that went to mediation, sales cancelled by the seller, and delayed dispatches. The result is painted on the colored thermometer that decides your search exposure and your eligibility for promotions. The exact tolerance percentages per country are not clearly published in open sources — what circulates on blogs is not reliably attributed to Mexico — so there too the authoritative source is MercadoLibre’s official help center and your own panel.

What can be stated without risk is the structure: in both cases the measurement is over a window that drags, not over the day. A bad December does not end on December 31; it keeps weighing on your number well into February.

what to do with listings after your cutoff

Shutting everything off is not the answer. There are four moves, and you want them decided before the day arrives.

• Change the shipping service, not the listing. If you have an express option available and the margin can absorb it, your cutoff moves several days. It is the cleanest exit: you keep selling with a promise you can actually keep.
• Adjust the published handling time. Raising it reflects reality and moves the estimated date the buyer sees. It converts less, but it converts honestly.
• Restrict by zone. Short-transit zones can stay active days after distant ones have closed. This requires a differentiated promise, not a single one for the whole country.
• Stop promising pre-Christmas and say so. A listing that keeps selling with January delivery, stated plainly, is a legitimate business. What is not legitimate is letting the buyer assume it lands by the 24th.

SKUs living in FBA or Full have a real advantage here: their cutoff is managed by the marketplace network and is usually later than yours. That is part of the cost-benefit of marketplace fulfillment, and it is an argument for having parked your fastest-moving products there before the season. The other side of that same coin is in self-fulfillment and last mile.

Glossary: real available stock, what you can truly sell today →

the promise and the stock are the same problem

There is a trap that only shows up in December and that breaks the promise without anyone touching handling time: promising against inventory that is not where you think it is.

If the stock you see in one channel is already committed by sales in another, every order that lands after that point is born with no unit assigned to it. Handling time does not stretch because you pack slower: it stretches because there is nothing to pack. And the buyer does not distinguish between “my packing bench got swamped” and “I sold something I did not have”: both look equally late from their side.

That is why the delivery promise and inventory sync are the same topic. A promise computed on a stock number that refreshes every few hours is a promise computed on the past, and in peak season the past from four hours ago no longer describes reality.

how this looks in iqseller

The panel does not generate labels, does not quote carriers and does not publish the delivery promise on your listing: that lives in Seller Central, in the MercadoLibre panel and in your shipping platform. What it solves is the input to the calculation, which is where most sellers operate blind.

The Inventory module keeps real available stock consolidated — FBA, Full, your warehouse, your 3PL — aligned with what each channel publishes, so what you promise is backed by units that exist and are not already committed on another channel. That is the floor of any serious promise.

Alerts flags when a SKU crosses its critical threshold or when sales velocity accelerates, which is precisely the moment the published promise stops being realistic and you need to adjust it or close the distant zone.

Profitability supplies the number that decides whether paying for an express service to move your cutoff is worth it: net margin per SKU with COGS you loaded, commissions from the Amazon settlement and MercadoLibre orders, FBA and Full fees, shipping, advertising, VAT and withholdings deducted. If a SKU’s margin cannot absorb the faster freight, the decision is to close the promise, not to eat the cost.

What the panel does not do is compute your transit time by postal code or measure your handling time: you measure those two in your own operation and in your carrier’s reports. The panel tells you how much margin and how much stock sits behind each decision.

the dashboard for the last two weeks

Five numbers, reviewed daily from December 10 onward:

• Your real handling time over the last seven days, as a median, not an average. The average hides the long tail.
• Promise cutoff date per delivery zone, written down and visible to whoever is covering, not living in one person’s head.
• Orders pending dispatch for more than 24 hours, as a named list, not as a count.
• Real available stock per SKU and per channel, so you do not promise against committed units.
• Late shipments and open claims for the period, with the end date of the window that measures them, so you know how long it will keep weighing on you.

What this changes is not the logistics: it changes who makes the decision. It stops being a gut call on December 22 and becomes a date agreed on the 1st, with criteria and numbers behind it.