Define the CDMX service area and device reality
Ciudad de México is one city but a website may serve only selected alcaldías, a pickup radius, a delivery zone, or a national market from a CDMX base. Put that boundary in the brief. The city’s open-data portal publishes an INEGI Censo 2020 dataset about homes with internet access, with variables processed for breakdowns by alcaldía, locality, and AGEB. The dataset is historical, so do not treat it as a current demand forecast. Use its documented geographic units when deciding which service-area pages or delivery rules deserve testing.
On a phone, show the service area, price, delivery or pickup terms, hours, and a working contact path without forcing heavy animation or an account before the first useful answer. If English supports a cross-border audience, decide which pages need it and keep Spanish as the operational and legal source. Never turn a CDMX neighbourhood name, domain suffix, or generic “we serve the city” phrase into proof of coverage.
Make Spanish the operational source of truth
For a Mexican online store, language and consumer information are product requirements. PROFECO’s public Virtual Stores monitoring tool lets people review fields such as contact details, total amount, prices in national currency, product or service characteristics, payment methods, privacy notice, cancellation, and shipping information. PROFECO’s voluntary e-commerce Code of Ethics lists a similar requirements conversation for participating stores: Spanish purchase information, RFC and contact details, terms, returns, payment and billing, security, total costs in Mexican currency, receipts, and delivery terms. The code’s voluntary status matters; use it as a documented checklist and confirm the legal obligations that apply to the business.
Put the Spanish version first in the content inventory, then map any English version to the same product names, prices, stock rules, cancellation language, and support hours. Ask who approves changes and how the two languages stay synchronized. A translated marketing page with an untranslated checkout, privacy notice, or error state can create a legal and operational gap. Include content entry and review for the buyer’s real states, not just a translated navigation label.
Plan payments and CFDI before visual polish
A Mexico City commerce project can need more than a payment button. SAT guidance says that when fiscal rules require a receipt, taxpayers issue a digital tax document through the SAT system. Its invoice requirements page lists fields such as the issuer and recipient RFC, tax regime, fiscal postal code, invoice use, service description, values, taxes when applicable, and payment method. Ask whether the site will collect the data for a later invoice, call an invoicing provider, or generate a handoff for staff; do not assume that a designer’s form meets the fiscal rules by itself.
Banco de México describes CoDi as a mobile payment and collection platform using QR and NFC, available around the clock and without an additional transaction commission in its description. It is an option to investigate, not a universal requirement or an endorsement of a particular bank. A quote should separate card or wallet fees, payment-provider account work, CoDi evaluation, refunds, reconciliation, and the CFDI workflow. Test a successful payment, a failed payment, a duplicate attempt, a refund, and the Spanish confirmation before launch. A low visual quote can become expensive when the handoff is vague.
Compare CDMX quotes in pesos and scope
Ask for a dated quote in Mexican pesos with tax treatment, third-party fees, payment schedule, and assumptions. Count templates, pages, product or service records, content loading, Spanish review, English scope, form states, checkout, invoice handoff, privacy and terms pages, analytics, migration, accessibility, training, hosting, and maintenance. A purely hypothetical comparison could be: Quote A, MXN 32,000 for an eight-page Spanish marketing site; MXN 9,000 for four English pages; and MXN 4,000 for a payment-link and invoice handoff, for MXN 45,000 before hosting, tax, and provider fees. Quote B, MXN 58,000, could include bilingual CMS templates, a product catalogue, payment testing, a documented fiscal handoff, mobile QA, training, and 30 days of fixes.
These invented figures are for scope comparison, not a CDMX market quote. Ask whether the Spanish copy is supplied, whether MXN prices include applicable IVA, who pays payment fees, whether a provider account is required, and what happens when a product, tax field, or delivery rule changes. A search result that advertises a low starting price may describe a template or a limited page count; it is not comparable until scope and date are written down.
Use alcaldía and fulfillment in a worked example
Imagine a fictional CDMX food cooperative selling subscription boxes with English information for visitors or partners. Its first scope decision is whether customers request a box through a Spanish form and receive a manual confirmation, or choose a delivery slot and pay in a full store. The second needs stock rules, delivery zones, cut-off times, payment status, refunds, receipts, and recurring-order changes.
Use the Censo dataset’s geographic structure as a prompt to define the zones, then replace the hypothesis with the cooperative’s actual coverage and delivery policy. Build the acceptance test around one Spanish purchase: select a box, read the total and delivery terms, enter the required fiscal information if applicable, pay or submit, receive confirmation, and find support. Repeat the critical states in English if that language is offered. It simply prevents a vague “CDMX delivery” promise from hiding a missing operational rule.
Use provider pages as attributed scope examples
The CDMX seed search led to CloudStudio’s own site, which describes a company founded in 2018 with a Mexico City base and lists enterprise platforms, high-volume ecommerce, and digital operations. Its page describes eight delivery phases, from discovery and signed milestones through design, QA, launch monitoring, and maintenance, and says proposals are built by scope. These self-described scope claims are useful comparison prompts, not an independent review, ranking, or proof that the process fits a small project.
Ask every provider for the equivalent facts: who owns the domain and accounts, which payment and invoice systems are supported, where data is stored, what the Spanish content review covers, how support is reached, and what is included after launch. Save the public page and date, but let the proposal, contract, test record, and handoff determine the decision. A local address can help a meeting or procurement requirement; it does not replace evidence that the team can deliver your exact commerce and language workflow.
Sign off with consumer and handoff evidence
Before signing off, keep a dated checklist for service area, Spanish source, English scope, product data, MXN prices, total and delivery terms, privacy, returns, contact, payment states, CFDI handoff, accessibility, analytics, ownership, backups, and support. PROFECO, SAT, Banxico, and CDMX datasets answer different questions; use each for the requirement it documents. Confirm legal and tax applicability with the responsible adviser.
A good CDMX decision is the proposal that makes the real customer and operator journey testable: a person can understand the offer, pay or request it, receive a reliable confirmation, and find help, while staff can reconcile the outcome and update the content. Recheck software fees, tax fields, delivery zones, language responsibilities, and provider packages before launch. Keep all quote arithmetic labelled as hypothetical and recheck missing local data before launch.
Plan a project with Dardo
Plan a project for Mexico
Choose a review date and a time in Bogotá to see the corresponding local time. This is a planning aid, we’ll confirm availability when we reply.
America/Mexico_City — Representative time zone; some countries have more than one. Check the actual city and agree on a working window. Dates include seasonal clock changes through your browser’s time-zone data.
Budget currency to discuss: MXN. The project calculator lets you enter your own rate. It does not convert exchange rates.
Let’s make it happen.
Send your result and project details directly to Dardo. We’ll review them and reply to your email. Review the included details below before sending.
Prefer email? hello@dardo.studio
Sources & further reading
Sources behind this guide, with further detail from the original publishers.
- Portal de Datos Abiertos CDMX / INEGI: homes with internet access, Censo 2020
- PROFECO: Virtual Stores Monitoring
- PROFECO Digital Distinction: e-commerce Code of Ethics requirements
- SAT: invoice requirements
- Banco de México: CoDi digital payments
- CloudStudio: web design and development in CDMX