Of the sixteen countries in Fufills' LATAM footprint, Puerto Rico is the only one where we operate as a registered local merchant. The entity is FUFILLS LLC, SURI registry 1639264-0010. Everywhere else — Mexico, Brazil, Colombia, the Central American cluster, Andean countries, the Southern Cone — we serve cross-border merchants through partner infrastructure with our SOPs overlaid.
This piece is the operator-side explanation of why PR specifically, and what we have learned running there.
Three reasons that all point in the same direction.
Reason 1 — PR is the only LATAM market that uses USD natively. Every other LATAM country requires the COD platform to manage local-currency collection plus USD conversion plus USD remittance. PR is the single market where the buyer pays the carrier in USD, the carrier remits in USD, and the merchant receives USD — same currency end-to-end. That collapses the FX risk to zero, which makes PR the cleanest market to run a settlement cycle on.
Reason 2 — PR sits inside US legal frameworks while being a LATAM market culturally and linguistically. A cross-border merchant who wants to learn COD in Spanish-speaking LATAM without immediately taking on a Spanish-language carrier landscape, a non-US contract jurisdiction, and a non-US-dollar currency can start in PR. The market is Spanish-first, the operations are LATAM-shaped, but the contract law and the currency are US-shaped. That makes it the natural training market.
Reason 3 — PR has a real, registry-verifiable local-merchant pathway. The SURI Hacienda registry produces a verifiable filing. We hold one. That makes PR the one place where Fufills can transact with merchants from any jurisdiction with all the legal predictability of a US-domiciled fulfillment relationship — and still deliver real LATAM COD operational learning.
Six things we have learned running PR that have generalized into the broader stack:
The disposition codes that matter are bilingual. PR calls happen in a mix of Spanish and English, often inside the same call. Disposition coding has to map both languages onto the same outcome. Mainland LATAM markets are usually monolingual at the disposition level; PR forced us to clean up the schema first.
Address informality looks different. PR has a US-zip-code system but real-world addressing often uses "near such-and-such" Spanish landmarks. The address-validation SOP had to handle both at once. That dual-mode validation later helped in mainland-LATAM cities where similar patterns appear at a smaller scale.
Carrier multi-tenancy is sharper here. PR's last-mile carrier landscape is dense for the geography. Running multi-carrier execution in PR taught us that performance-window evaluation needs a shorter rolling window than we initially used — 2 weeks instead of 4, on accounts where order density is high.
Cash-handling at the door is rare but consequential. USD cash at the door in PR is less common than in mainland LATAM (cards and Visa-style transfers absorb more share), but when it happens the buyer expects exact change and a printed receipt. That forced us to operationalize a printed-receipt SOP earlier than the rest of the book required, and it became a quality differentiator everywhere.
Returns logistics is tight because the geography is bounded. A PR return goes to a single fulfillment hub. The SOP we wrote for PR returns generalizes well to mainland-LATAM islands (DR) and to compact country geographies (El Salvador, Costa Rica).
Compliance is end-to-end visible. Because PR sits inside US federal tax and consumer-protection law, every operating decision has a compliance shadow. That has been useful: it forced us to write down what we do, in a form that holds up to audit. The same documentation is now the basis for our published SOPs.
The pattern we recommend for merchants entering LATAM through Fufills is roughly:
- Pilot in PR. USD end-to-end. Spanish-language call center. Short ground-truth feedback loops. Two to three weeks is enough to test the SKU economics, the COD adoption among the buyer audience, and the merchant's tolerance for the reconciliation rhythm.
- Read the PR data with a clear head. PR is not perfectly representative of mainland LATAM — COD share is lower, AOV is higher, FX is removed. But the operational lessons (confirmation discipline, packaging discipline, returns handling) generalize.
- Pick a mainland pair. One band-1 country for volume (Mexico, Brazil, Colombia) and optionally one band-2 country for capture (Guatemala, Ecuador, DR). See the state-of-play piece for the band logic.
- Add countries on a quarterly cadence. Adding more than 2 new countries inside a single quarter saturates the operational onboarding. Adding 1–2 per quarter is sustainable for most merchants.
PR is rarely the country where most volume eventually lives. It is the country where the learning happens cheapest.
Three honest answers:
We would set up the PR entity earlier. The Wyoming entity came first; PR followed. In retrospect, having SURI registry visible from week one of the merchant relationship would have shortened the trust-building cycle with our earliest cross-border merchants.
We would publish PR-specific operating data sooner. A merchant evaluating PR as a launchpad benefits from seeing PR-specific COD share, AOV bands, RTO curves, settlement timing. We are now publishing those into the PR country page and will update quarterly.
We would build the bilingual call-center playbook from PR first, not adapt it from mainland. We did it backward and re-did it. The PR-first version is cleaner.
Every operating principle Fufills publishes about LATAM COD — hard-gated confirmation, multi-carrier execution, 7-day settlement, regional SOP standardization — was either invented in PR, broken first in PR, or stress-tested in PR before being rolled out across the rest of the 16-country footprint.
That is what we mean when we say PR is the launchpad. Not for the merchant. For us, first. The merchant inherits what we have already broken and fixed.