Contents
- The crossing is a distribution, not a duration
- Clearance is a formal process, which is why it cannot be rushed on the day
- One promise cannot cover the whole country
- Building a window that survives the tail
- Local stock changes the arithmetic entirely
- What to tell the buyer when the tail lands
- The three legs, measured separately
- Two timestamps that make the crossing measurable
- Carrier mix inside Mexico is a coverage decision
- Attempt policy is part of the promise
- Peak season moves every number in the same direction
- How the promise interacts with marketplace metrics
- What good looks like after 90 days
- Writing the promise so it reads as a commitment
- How BringGo Ship Handles This
- Frequently asked questions
A delivery promise is the only forecast a seller publishes to buyers, and it is judged with a single day of tolerance. Cross border into Mexico it has three moving parts rather than one: the domestic leg in the United States, the crossing, and the domestic leg in Mexico. Sellers who model only the third and add a fixed number for the rest are wrong in both directions on different orders.
The crossing is a distribution, not a duration
A cleared shipment moving from a Laredo facility toward Monterrey covers roughly 3 hours of driving. That is the smallest component. The variable part is customs: a shipment released on the green light reaches the destination warehouse in 1 to 2 business days, and a physical inspection on the red light adds 1 to 2 days on top of that.
So the crossing is not a number, it is a range with a tail. A promise built on the median breaks every time the tail lands, and the tail is assigned per entry rather than per seller.
| Outcome | Time to destination warehouse | Effect on promise |
| Green light | 1 to 2 business days | Promise holds |
| Red light, inspection | Add 1 to 2 days | Promise breaks unless buffered |
| Documentation query | Open ended until resolved | Requires proactive notice |

Clearance is a formal process, which is why it cannot be rushed on the day
"Para efectos de esta Ley, se entiende por despacho aduanero el conjunto de actos y formalidades relativos a la entrada de mercancías al territorio nacional y a su salida del mismo."
Ley Aduanera, Article 35
The practical reading is that the levers which shorten a crossing are all pulled before the truck moves. A complete document set, a settled tariff classification and an entry filed by a broker who has what they need. Once the shipment is at the border, the seller has no remaining lever except patience.
"En México solo un agente aduanal con patente puede presentar el pedimento."
Servicio de Administración Tributaria
What the tracking feed can honestly report while a shipment is in customs is covered in Door to Door US to Mexico: What Tracking and Proof of Delivery Actually Prove.
One promise cannot cover the whole country
Mexico is not a single delivery geography. A destination in the Monterrey metropolitan area is a short domestic leg from a northern facility. A destination in the south or in the Yucatán is a different transport problem entirely, and no amount of customs efficiency changes that.
The fix is not a longer national promise. A single promise stretched to cover the slowest destination is wrong for the majority of orders, and it loses conversions in the cities where the seller is actually fast. Promise by zone instead, and let the checkout show the number that applies to the postal code the buyer entered.
- Northern metros. Shortest domestic leg from a border facility, and the zone where a local stock position pays off most.
- Central corridor. Longer domestic leg, still well served by ground.
- South and peninsula. Longest leg, and the zone where carrier coverage varies most by postal code.
Building a window that survives the tail
Take the components separately and add a buffer sized to the variability rather than to the average. A promise of 1 to 2 business days for the crossing plus a zone specific domestic leg produces a range. Publishing the upper end of that range is not pessimism, it is the number that will be true on the days when the entry draws an inspection.
The alternative, publishing the median and apologizing on the tail, costs more than the conversions the shorter number wins. A late delivery on a first order is a lost second order, and the second order is where the margin is.
Local stock changes the arithmetic entirely
Every problem above belongs to shipments that cross after the order is placed. Stock already inside Mexico has crossed already, and the promise reduces to a domestic leg with no customs variance at all.
This is the strongest argument for holding stock locally on fast moving SKUs, and it is an argument about promise reliability rather than about cost. The same order that carries a 4 to 7 day cross border window carries a 1 to 3 day domestic window when it ships from local stock.
What to tell the buyer when the tail lands
The guarantee period in Mexican law runs from delivery, and it is longer than many sellers assume:
"Para los efectos del párrafo anterior la garantía no podrá ser inferior a noventa días contados a partir de la entrega del bien o la prestación del servicio."
Ley Federal de Protección al Consumidor, Article 77
That matters here because a late delivery does not shorten the obligation that follows it. A buyer who receives a package 4 days late still has the full statutory guarantee from the day it arrived. Handling the delay well is therefore not only a service decision, it changes whether the customer uses that window to return or to reorder.
Proactive notice on the day the exception occurs, with a revised date rather than an apology, is the single practice that converts a broken promise into a retained customer.
The three legs, measured separately
A promise built as one number cannot be diagnosed when it breaks, because there is no way to tell which leg failed. Measured as 3 legs it can be fixed, because each has a different owner and a different remedy.
| Leg | Owner | Typical variance | Remedy when it slips |
| US domestic to border facility | Origin carrier | Low, ground network | Carrier review, tender earlier |
| Crossing and clearance | Broker and customs | 1 to 2 days, tail on inspection | Document set completeness |
| Mexican domestic to buyer | Final mile carrier | Varies by zone and postal code | Zone specific promise, carrier mix |
Most sellers instrument only the third leg, because that is the one the tracking page shows. The second leg is where the variance lives, and it is invisible unless the entry date and the release date are both recorded.
Two timestamps that make the crossing measurable
Entry filed and goods released. The gap between those 2 is the crossing, cleanly separated from both domestic legs. Collect them for 90 days and the distribution appears: a median, and a tail whose frequency tells you exactly how much buffer the promise needs.
Without those timestamps, a seller experiencing 1 slow week cannot tell whether customs slowed, the origin carrier slowed, or the final mile carrier slowed, and the usual response is to blame the most visible one.
Carrier mix inside Mexico is a coverage decision
Coverage is not uniform, and a single national carrier will serve some postal codes well and others on an extended schedule. A mix routed by postal code produces a better promise than any single carrier, at the cost of more integration work.
The test is per postal code rather than per state. State level coverage claims hide the rural codes inside a state that is otherwise well served, and those codes are where a national promise breaks most often.
Attempt policy is part of the promise
What happens on a failed delivery attempt changes the effective delivery date more than the transit time does. A carrier making 2 attempts and then holding at a branch produces a different buyer experience than one making 1 attempt and returning the parcel. The second policy turns a minor timing miss into a return, and the return costs the outbound freight, the return freight and the sale.
Ask for the attempt policy in writing before the rate, because it is the term that decides how many deliveries actually complete.
Peak season moves every number in the same direction
In the fourth quarter the domestic networks on both sides run at capacity, customs volumes rise, and the same entry that clears in 1 day in March can take longer in November. A promise that was accurate for 9 months of the year becomes optimistic in the tenth.
The correct response is a seasonal promise rather than an annual one. Publish a longer window for the peak weeks, set it before the season rather than during it, and keep the local stock position deep enough that the orders which can avoid a crossing do avoid it.
How the promise interacts with marketplace metrics
On a marketplace the promise is not only a buyer facing message, it is the benchmark the platform measures against. A shipment despatched inside the handling time but delivered outside the estimated window affects different metrics than one despatched late, and the two failures have different fixes.
Separating them requires 2 dates rather than 1: the date the parcel left the facility and the date it was delivered. A seller tracking only delivery date will read a crossing delay as a handling failure and try to fix the warehouse, which was never the problem.
What good looks like after 90 days
Four numbers, reviewed monthly. Promise accuracy by zone rather than nationally. Crossing time distribution with the tail frequency stated. Failed first attempt rate by carrier. And the share of orders served from local stock, because that is the lever that removes the crossing from the promise entirely.
When promise accuracy falls, those 3 other numbers say which leg caused it. Without them the only available response is to widen the promise, which is the fix that costs conversions everywhere in order to solve a problem that existed in one zone.
Writing the promise so it reads as a commitment
The wording carries as much weight as the number. A range stated as 4 to 7 business days with the counting rule visible reads as a considered estimate. The same range stated as roughly a week reads as a guess, and a buyer who reads a guess treats a miss as carelessness rather than as variance.
Three details make the difference. State whether the count begins at order or at despatch, because those are different days on a marketplace with a handling time. State business days explicitly where customs is involved. And show the zone the estimate applies to, so a buyer in a slower region sees their own number rather than a national average they will not experience.
The coverage tiers underneath those transit times are set out in Last Mile Across Mexico: Coverage, Postal Codes and Attempt Policy.
How BringGo Ship Handles This
BringGo Ship measures the three legs separately and reports them back: the US domestic leg, the crossing from entry filed to goods released, and the Mexican final mile. Our team builds zone specific promises rather than one national number, routes by postal code across a carrier mix, and buffers the published window for a customs inspection. When an exception happens, sellers get a revised date on the day rather than an apology afterwards.
Frequently asked questions
Should the promise include weekends? Publish business days for the crossing, because customs operates on business days, and calendar days for the domestic leg where the carrier delivers on Saturdays. Mixing the two silently is how promises drift.
How much buffer is too much? Enough to cover an inspection, which is 1 to 2 days. Beyond that the promise stops being competitive without becoming meaningfully more reliable.
Can I show a different promise for local stock? Yes, and you should. It is a different fulfillment path with a different variance, and showing one blended number understates your best case and overstates your worst.
James Carter
Warehousing and Fulfillment Operations
Writes on Amazon Mexico and e-commerce fulfillment across the Laredo border.
View profile