Follow the order's origin before comparing delivery
“Rappi delivery” can describe two different operating arrangements. In a marketplace order, the customer shops and orders through Rappi. With a delivery service for your own channel, the customer orders from your business and a courier fulfills the delivery request.
Rappi's Mexico merchant overview describes its marketplace and full-service delivery model. Cargo by Rappi's Mexico offering describes requesting delivery services for businesses, manually or through integration. Neither label alone establishes availability or terms for every store.
The useful decision is not which logo appears on a courier's bag. It is where the order, payment, customer communication, and support responsibility begin.
Separate discovery, checkout, and fulfillment
For a Rappi marketplace order, the listing and marketplace customer journey are part of the channel. The restaurant needs the relevant merchant account and must operate the menu, acceptance, preparation, and commercial agreement for that channel.
For an own-channel order fulfilled with Cargo, your website, app, phone team, or other ordering channel creates the sale. The delivery request needs pickup and destination information, preparation readiness, the applicable quote, and tracking. Cargo should not be treated as a source of marketplace demand for that order.
Using both can make sense operationally, but keep the records distinct. A marketplace order and an own-channel order should not be merged simply because the same delivery network is involved.
Walk an own-website order through Cargo
Imagine a customer orders dinner on the restaurant's own website. The restaurant controls the menu and checkout flow, confirms the service address, and presents the applicable delivery charge before the customer commits.
The accepted order then becomes a delivery request through the configured Cargo workflow. Staff communicate when the meal is ready, match the order and courier references at pickup, and follow delivery status. The restaurant's support team needs to see the original order and the delivery reference together.
If the customer cancels before pickup, test whether the ordering and delivery requests both reach the intended final state. After pickup, a different support or return process may apply. Do not assume that refunding the food payment automatically cancels a trip already being performed or removes every contracted delivery charge.
Compare the cost and data boundaries separately
For the marketplace channel, obtain the account's fee basis, taxes, promotions, adjustments, settlement schedule, and customer-support terms. For Cargo, obtain the applicable delivery pricing, geographic coverage, failed-attempt and cancellation terms, and any integration or service conditions.
Compare completed orders and failed orders, not just a successful trip. Include payment processing and the team's support work on an own-channel sale. A delivery quote is one cost component; it is not the platform's whole cost of acquiring, taking, preparing, and supporting an order.
The data boundary also changes. A restaurant can record the customer relationship created through its own channel under its policies and permissions. That does not grant access to unrelated Rappi marketplace customers or transfer rights to market to them. Preserve the contractual and privacy boundaries of each channel.
Use the correct Ordering.co connection
Ordering.co's Rappi marketplace integration publishes the supported menu, receives Rappi orders, and sends order status back. Its Rappi Cargo integration requests delivery for your own-channel orders, with quote, dispatch, and status behavior described on that integration page.
Validate the actual merchant accounts, country, store mapping, and provider setup. A listed integration does not approve the restaurant's Rappi account or guarantee courier capacity at every address and hour.
Keep one menu authority and clear responsibility for each order. For example, distinguish the staff action that accepts the food order from the provider event that assigns a courier. The two events solve different problems even when they appear in one operating workspace.
Accept each channel with its own failure tests
Run one marketplace order and one own-channel Cargo delivery with a representative menu. Confirm customer-visible charges, the order reference, pickup readiness, status updates, and the final financial records.
Then test an address without service, an unavailable courier, a delayed kitchen, a repeated delivery request, and cancellation before pickup. Make the support owner explain the customer's next step without asking staff to guess which channel holds the payment.
If the restaurant is not yet registered, begin with the Rappi onboarding guide. If it already operates its own ordering channel, start with the Cargo account and delivery requirements. Choose the problem to solve before combining the services.