RiderX Delivery Sync
Two-way sync between WooCommerce orders and the RiderX delivery platform, including live delivery rate quotes at checkout.
Use with caution
RiderX Delivery Sync works, but test it on a staging site before relying on it in 2026. Was last updated 1 month ago, and scores 55/100 on our health check.
- Small user base (<10 active installs)
- Very few reviews so far
How does it stack up?
Side-by-side on installs, updates, ratings & supportDaily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where RiderX Delivery Sync stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| delivery | >100 |
| logistics | >100 |
| riderx | #1 |
| shipping | >100 |
| woocommerce | >100 |
About RiderX Delivery Sync
From the official readme · v1.0.59Description
RiderX Delivery Sync connects your WooCommerce store to the RiderX delivery platform. It quotes live delivery rates at checkout and dispatches paid orders to RiderX for fulfilment, keeping order delivery status in sync.
Features:
- Live delivery rate quotes shown as a WooCommerce shipping method (classic and block checkout).
- Rate breakdown displayed in the shipping label (distance, estimated time, net price, VAT).
- Automatic dispatch of orders to RiderX when payment is received.
- Configurable restaurant / pickup location and credentials.
- Works with WooCommerce High-Performance Order Storage (HPOS).
This plugin communicates with the RiderX delivery service to obtain rates and create deliveries. A RiderX account and API credentials are required.
External services
This plugin uses external services for delivery orchestration and optional admin map visualization:
-
RiderX API (required for core functionality)
- Service URL: https://riderx.me
- Purpose: Request delivery rate quotes, dispatch deliveries, and read live delivery status.
- Data sent: Pickup and delivery addresses, customer phone, customer email, order total, currency, item count, and optional pickup schedule.
- Terms: https://riderx.me
-
OpenStreetMap tile service (optional, admin delivery-history maps)
- Service URL: https://tile.openstreetmap.org
- Purpose: Render map tiles in the plugin admin delivery history detail view.
- Activation: Used only when “Enable external map services” is enabled in plugin settings.
- Data sent: Map tile coordinates requested by the browser while rendering the admin map.
- Terms: https://operations.osmfoundation.org/policies/tiles/
-
OSRM demo routing service (optional, admin delivery-history route line)
- Service URL: https://router.project-osrm.org
- Purpose: Draw pickup-to-customer route geometry in the admin delivery history detail view.
- Activation: Used only when “Enable external map services” is enabled in plugin settings.
- Data sent: Pickup and customer latitude/longitude coordinates.
- Terms: https://project-osrm.org/
Installation
- Upload the plugin folder to the
/wp-content/plugins/directory, or install it through the WordPress plugins screen. - Activate the plugin through the “Plugins” screen in WordPress.
- Go to WooCommerce settings and enter the unique Store Middleware Key issued for this store, your RiderX Client ID and Client Secret from the RiderX Developer Console, and this store’s sender contact and pickup location.
- Enable the RiderX delivery shipping method in your shipping zones.
- Copy the Inbound Webhook URL from the RiderX settings screen and register it in your RiderX partner panel.
- Paste the webhook signing secret that RiderX returns back into the Webhook Signing Secret field, so delivery status callbacks can be verified.
Frequently asked questions
Do I need a RiderX account?
Yes. You need RiderX API credentials to request rates and dispatch deliveries.
Does it work with block checkout?
Yes. The delivery rate and its breakdown are shown in both classic and block (React) checkout.
Changelog
Stops dispatching orders that did not actually ship via RiderX, and adds automatic retry for a dispatch that fails from a brief network or server error.
1.0.59
- Fixed orders being dispatched to RiderX regardless of which shipping method was actually chosen. The processing-status hook fired for every order, so one shipped with flat-rate to an address hundreds of kilometres outside the RiderX service area would still be sent to RiderX and logged as “Dispatch failed” once RiderX (correctly) couldn’t handle it. Orders are now dispatched only if their shipping line is actually RiderX Delivery.
- Added automatic retry for a dispatch that fails with a transient error (a bare connection failure, or HTTP 429/500/502/503/504). Up to two more attempts run within the same request a couple of seconds apart, which recovers a momentary edge/origin blip without any manual action. If it is still failing after that, one more attempt is scheduled automatically a few minutes later, up to two rounds, before it is left for manual resync. A non-retryable failure such as a bad request is not retried, since retrying broken input only wastes calls and floods the order notes.
1.0.58
- Stopped quoting a delivery price before the customer has entered a street address. A postcode and city alone geocode to the middle of the district, so the cart showed a distance and a price that had nothing to do with the real destination and changed once the address was completed. The RiderX rate now appears only once a street line with a house number is present.
- Other plugins’ licence reminders and upsells are no longer rendered on the RiderX settings screen. WordPress, WooCommerce and this plugin’s own notices are untouched, and every other admin page is left exactly as before.
1.0.57
- Fixed the Preferred Delivery Time field being invisible to most customers. It was registered in the shipping fieldset, which WooCommerce keeps hidden unless the shopper ticks “Ship to a different address”, so a normal order could never choose a delivery time. It now sits with the order notes, where it is always shown.
- Fixed Test Middleware Connection always reporting a 404. It sent a GET to the rate endpoint, which only accepts POST, so a perfectly healthy service looked broken. It now checks /health and explains what the result means.
- Removed the Dispatch Endpoint preview that showed api.riderx.me, a host that was decommissioned and never used for dispatch. The field now shows the real endpoint, derived from the Middleware Base URL.
- The Environment switch no longer implies it changes servers. Which RiderX environment is used is decided by the middleware; the setting is now documented as a label.
1.0.56
- Clarified that the Store Middleware Key is unique per store and issued by the middleware administrator. It is not a shared environment key, Mapbox token, or RiderX credential.
1.0.55
- Normalizes sender phone country codes to digits only before sending them to the middleware and RiderX (for example,
43instead of+43).
1.0.54
- Added required per-store sender contact fields (full name, email, and phone) and sends them with every delivery request. WooCommerce orders no longer inherit middleware or kiosk sender defaults.
- Treats missing RiderX Client ID, Client Secret, or sender contact as incomplete configuration so a store cannot silently dispatch under shared or placeholder identity.
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best RiderX Delivery Sync alternatives
All delivery plugins →FAQ
RiderX Delivery Sync: quick answers
Straight answers, pulled from live WordPress.org data.
Live data from WordPress.org · checked Oct 2, 2026
Is RiderX Delivery Sync free?
Yes. RiderX Delivery Sync is free to download and use from the official WordPress.org plugin directory.
Is RiderX Delivery Sync safe to use in 2026?
RiderX Delivery Sync works, but test it on a staging site before relying on it in 2026. Was last updated 1 month ago, and scores 55/100 on our health check.
How many websites use RiderX Delivery Sync?
RiderX Delivery Sync is active on <10 WordPress websites and has been downloaded 481 times since it launched in June 2026. It was downloaded 69 times in the last 30 days.
Does RiderX Delivery Sync work with WordPress 7.1?
RiderX Delivery Sync is officially tested up to WordPress 7.0.6, while the latest release is 7.1.2. It may still work, but try it on a staging site first.
What PHP version does RiderX Delivery Sync need?
RiderX Delivery Sync requires PHP 7.4 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was RiderX Delivery Sync last updated?
The latest version, 1.0.59, was released on August 25, 2026 (1 month ago).
Who makes RiderX Delivery Sync?
RiderX Delivery Sync is developed and maintained by riderx.
What are the best alternatives to RiderX Delivery Sync?
The most popular alternatives to RiderX Delivery Sync are SMTP2GO for WordPress (30K+ installs), Claudio Sanches (20K+ installs) and Packlink PRO for WooCommerce (20K+ installs).
Powered by PageForge
Want thousands of pages that rank like these? Build them in an afternoon.
This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages — with schema, internal links and AI-written copy baked in.
- CSV, Google Sheets & API data sources
- AI content, schema & internal links per page
- Works with Elementor, Gutenberg, Yoast & Rank Math
- Free on WordPress.org — no credit card