Use the restaurant-partner route for the correct country
Registering a restaurant on Rappi is different from opening a consumer account or signing up as a courier. Start from the official merchant site, select the restaurant's country, and follow the partner-registration route.
The example here uses Mexico's published restaurant requirements, checked on October 21, 2026. Another country's documents, service coverage, and agreement can differ. The existing restaurant's physical location and legal entity should determine the registration, rather than whichever regional page appears first in search.
Choose who will own the partner account, maintain store information, receive operational messages, and review charges. Use an account the business can retain when staff change.
Prepare the entity and banking information
Rappi's Mexico requirements table lists RFC and identification for an individual; its corporate category adds legal-representative documentation, company formation documents, and bank certification. The current application determines which evidence your restaurant must submit.
Check consistency before uploading: the restaurant's operating name, legal name, tax information, address, representative, and settlement account must refer to the intended business. Do not solve a mismatch by entering a convenient name from another branch.
Use the official registration channel for sensitive documents. Keep a record of what was submitted and who can respond to a correction request. Approval remains Rappi's decision; having a menu and a tax identifier does not guarantee activation.
Register the menu the kitchen can actually serve
The official Mexico registration guide describes the business form and menu setup in Rappi Partners. Prepare clear item names, descriptions, prices, categories, and images, then check the choices that affect preparation.
Use structured required modifiers where the selected setup supports them: size, side, or a paid addition should not depend on someone interpreting a note. Review unavailable products, opening hours, packaging, and the time the kitchen needs before pickup.
For example, a burger with a required side and a paid extra should appear to staff with the same selections and total the customer saw. Test that example before adding every item from a printed menu. Publication quality matters more than a large catalog that the shift cannot operate.
Read the operating and commercial terms before activation
Identify the delivery model offered to your account, where it applies, who handles customer support, and what happens when an order is rejected, canceled, or cannot be delivered. Rappi's Mexico merchant overview describes its marketplace and full-service delivery proposition; the applicable account agreement determines the terms you accept.
Ask for the service-fee basis, taxes, payment schedule, funded promotions, adjustments, and any other contracted charges. Do not treat a headline commission as the entire cost or import a percentage from another country.
Keep the order reference, any refund or adjustment, the provider's charge record, and settlement reference connected. The money deposited in the bank may reflect multiple orders and deductions; it is not a substitute for an order-level operating review.
Prepare the team for the first accepted order
Before starting service, confirm the device, connection, notifications, and people responsible for acceptance and preparation. Rehearse a normal order, an unavailable item, a late preparation, and a cancellation through the supported merchant workflow.
During an illustrative first order, staff match the reference and modifiers, accept with a realistic preparation plan, pack the correct items, and confirm the courier handoff. If something fails, the shift needs an escalation owner rather than a guess about which app will fix it.
Review the first operating period against menu accuracy, missed alerts, preparation handoffs, customer issues, and the corresponding financial records. Registration is complete as an administrative step before the operation is necessarily ready to scale.
Distinguish joining Rappi from connecting Ordering.co
Rappi approves and operates the merchant account. Ordering.co's Rappi integration connects the confirmed menu, incoming Rappi orders, and order-status flow to Ordering.co. Validate the actual store mapping and supported behavior before relying on the connection.
Your own restaurant website is a separate ordering channel. It does not automatically inherit Rappi's customer reach or account terms. Likewise, Rappi Cargo concerns delivery of orders from your channels, rather than the marketplace registration described here.
For the distinction between those fulfillment models, continue with Rappi marketplace delivery versus Cargo. This lets the restaurant choose separately how customers discover it, where they order, and who delivers.