Ordering.co vs X-Cart
X-Cart documents Marketplace and its Multi-Vendor add-on for stores with several sellers, vendor products, commissions, and payout records. Its current commercial site focuses on automotive commerce, while the Multi-Vendor setup guide sits in its Legacy documentation. Confirm the version, license, and supported offer for your project. Ordering.co connects your marketplace channels to merchant operations and local delivery; compare the complete operating model rather than only the shopping cart.
| Capability | Ordering.co | X-Cart |
|---|---|---|
| Native app for local drivers | Included | Not listed |
| Driver schedule activation | Included | Not listed |
| Driver proof of delivery | Included | Not listed |
| Included merchant and driver frontend code | Included | Not listed |
Ordering.co at a glance
- years building ordering technology
- 12+
- of orders a month, on auto-scaling infrastructure
- Millions
- products across ordering channels, operations, and delivery
- 20+
- features, from catalog to dispatch
- 1,500+
Enterprise brands running on Ordering.co technology
Why local marketplace builders evaluate Ordering.co
Start with the merchant and delivery work behind each sale. Confirm the shopping-cart and financial scope separately.
Connect the store to the order
Stores manage menus, hours, availability, acceptance, and preparation. The operator defines how independent merchants work within the marketplace.
Operate local delivery
Your drivers receive assignments and update progress from the Driver App, with customer tracking and delivery proof. A parcel shipping method is not the same operating test.
Build on supplied channels and code
Use marketplace web and branded apps with included open-source frontend code. APIs and webhooks connect only the provider workflows confirmed in your project.
Compare the work each platform must do
X-Cart behavior depends on the installed edition, Multi-Vendor version, and configured mode. Not listed refers to the supplied local-driver and operational frontend workflows in the cited material, not all X-Cart customizations.
| Capability | Ordering.co | X-Cart |
|---|---|---|
| Sellers, checkout, and money movement | ||
| Seller products and order access | Operate stores and merchants with their menus, hours, orders, and delivery; one checkout across stores works on web and app. | The Multi-Vendor documentation describes vendor product management and Warehouse or Vendors as Separate Shops modes, with different order visibility and handling. |
| Multi-seller checkout | One checkout across stores works on marketplace web and app, with a separate order and delivery time per store. | X-Cart documents carts involving multiple vendors. Demonstrate how the selected mode creates orders, invoices, shipping charges, cancellations, and refunds. |
| Payouts and reconciliation | Configure a supported merchant-payment provider and agreed commissions, settlement, and refund rules. Confirm connected-account eligibility. | X-Cart documents automatic distribution with supported payment methods or manual payouts outside the store, with transaction tracking. Gateway and add-on compatibility must be confirmed for your version. |
| Local merchant and delivery workflows | ||
| Native app for local drivers | A native Driver App connects assignments, live location, and PIN, photo, signature, or video proof of delivery to the order. | Not listed |
| Driver schedule activation | Configure driver schedule windows and automatic activation or deactivation; drivers can complete their last assigned order before deactivation. | Not listed |
| Driver proof of delivery | Capture a photo, signature, PIN, or video as proof attached to the delivery workflow. | Not listed |
| Included merchant and driver frontend code | Open-source web, customer app, Merchant App, Driver App, and Dashboard frontend code is included with every product. The backend is managed by default. | Not listed |
“Not listed” means the capability does not appear in X-Cart's product lineup. Confirm scope and terms with each provider.
Scope and costs to settle before choosing
Documentation and commercial scope checked October 21, 2026. Confirm the exact product before reusing any older Multi-Vendor offer.
An older add-on is not a current quote
Ask X-Cart to confirm availability, supported version, license, updates, hosting, support, and payment extensions for your Multi-Vendor project. Its current pricing page does not establish a universal local-marketplace price. Do not substitute an automotive package or an old license amount.
Settle hosting and maintenance ownership
Write down who hosts the deployment, performs upgrades and backups, maintains extensions and custom code, monitors failures, and restores service. Compare a supported hosting proposal and a self-managed installation only on their agreed responsibilities.
Prove local service separately from shipping
A vendor shipping configuration does not establish preparation capacity, store hours, service areas, driver assignment, or delivery proof. Include those tests and the staff who run them in the implementation cost.
Proven with enterprise brands.
The platform you would run on already runs ordering for Alsea, a multi-brand restaurant group with more than 4,000 locations.
Alsea runs WOW+ and ten restaurant brands on one ordering platform.Domino's, Starbucks, Burger King, Vips, and six more brands share one app, one website, call centers, and a delivery operation that assigns drivers automatically.10 brands on WOW+4,262 locationsMexico and ColombiaRead the Alsea storyPilot two sellers before moving the marketplace
Keep the installed X-Cart store live while you validate the checkout, vendor accounting, and local-order flow to replace.
What moves
Vendor catalog and identifiers
Map sellers, products, variants, categories, prices, stock ownership, tax rules, service areas, and store schedules. Preserve seller-product identifiers for reconciliation.
Balances, access, and exports
Request permitted customer and order exports, document commissions and unpaid balances, and retain payout records and invoices. Confirm domain, hosting, payment accounts, and extension licenses without assuming their transfer.
How the move runs
Identify the installed mode
Record X-Cart version, Multi-Vendor configuration, custom code, and payment distribution path. Agree which behaviors the replacement must preserve.
Test two sellers and a partial refund
Place a mixed cart, check fees and merchant order intake, assign delivery, cancel one seller’s items, and reconcile customer refund and vendor balance records.
Move accepted traffic and settle the old period
Train merchants, update the agreed domain and links, and keep access to historic orders and vendor balances until settlements and refunds are complete.
No automatic migration of X-Cart code, vendor balances, credentials, gateways, or hosting is implied. Confirm the current supported offer and the records your agreement lets you move.
Questions about X-Cart and Ordering.co
Is X-Cart Multi-Vendor the same as its current automotive offer?
Do not assume that. X-Cart retains Multi-Vendor documentation and an add-on listing, while its commercial site emphasizes automotive commerce. Confirm the supported edition and contract for the marketplace you intend to operate.
Are payouts automatic for every gateway?
No universal rule follows from the Multi-Vendor feature. Its docs distinguish supported automatic distribution from manual payouts. Check the actual gateway, connected seller accounts, order mode, commissions, and refund behavior.
Can we keep a working X-Cart backend and add a channel?
That requires a confirmed project boundary and integration. Identify catalog, stock, payment, and order-status authorities and test failures before promising coexistence. This comparison does not establish a native X-Cart-to-Ordering.co connection.
X-Cart and every other product name on this page are trademarks of their respective owners. Ordering.co is not affiliated with X-Cart.
Bring the installed marketplace and its obligations.
Compare two sellers, a mixed cart, a payout record, and one local delivery in an Ordering.co demo. Scope hosting, maintenance, data movement, and integrations in the proposal.