RouteMile for WooCommerce
| 开发者 | codermillat |
|---|---|
| 更新时间 | 2026年9月10日 22:38 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv3 or later |
| 版权网址: | 版权信息 |
详情介绍:
RouteMile turns a single-restaurant WooCommerce store into a full delivery operation. Customers drop a pin on a map at checkout; the store owner manages orders through a dedicated deliveries dashboard; riders work from an installable mobile web app.
Checkout
- Interactive map location picker (Google Maps with an API key, or a free OpenStreetMap + Leaflet mode with no key required)
- Distance-based validation — orders outside your delivery radius are blocked before payment
- Distance-based delivery fee: flat rate, per-km rate, or distance tiers, with an optional free-delivery threshold and minimum order amount
- Live fee update in the Order summary as the customer moves the pin
- Store opening hours: per-weekday schedule, "open all day" / "closed all day" toggles, and a special-occasion override
- Estimated arrival time shown to the customer (kitchen prep time + travel time)
- Deliveries dashboard listing unassigned, assigned, and out-for-delivery orders, including the customer's kitchen note
- Custom order statuses: In Kitchen → Assigned → Picked Up → Completed, each with its own WooCommerce email notification
- One-click assignment of delivery riders, with automatic reassignment handling
- "Accept Order" action to move new orders into the kitchen with one click
- Admin-bar toggle to open/close ordering instantly
- Rename the five order stages (labels, colours, icons) to match your restaurant's wording — shown in the admin, the rider app and customer tracking; order data itself is untouched
- Set a brand colour once and every plugin surface (checkout, tracking, My Account, rider app) recolours automatically, with WCAG-checked text contrast
- Installable PWA (Add to Home Screen) that looks and feels like a native app
- Live order list with New / In Progress / Delivered tabs and automatic refresh when new orders arrive or statuses change
- Per-order actions: call the customer, open the exact delivery location in maps, mark picked up / delivered
- Cash-on-delivery awareness: shows the amount to collect per order and a running "cash in hand" total
- Rider-initiated cash settlement requests that a manager or admin accepts or rejects, with a full audit ledger
- Riders see delivery instructions only — kitchen notes stay private to the store
- Order tracking page showing live status and, once assigned, the rider's name and phone number
- Reorder shortcut and an upgraded My Account dashboard with order stats and saved delivery address
- Thermal-printer-friendly receipt template
- Google Maps — JavaScript is loaded from
maps.googleapis.comon the checkout page; geocoding and routing requests are sent server-side tomaps.googleapis.com. Service: Google Maps Platform. Terms: Google Maps Platform Terms of Service. Privacy: Google Privacy Policy. - OpenStreetMap tiles — map tiles are loaded from
tile.openstreetmap.org. Service: OpenStreetMap. Terms / licence: OpenStreetMap Copyright and License. Privacy: OpenStreetMap Foundation Privacy Policy. - Nominatim geocoding (OpenStreetMap mode only) — coordinate and address lookups are sent to
nominatim.openstreetmap.org. Subject to the OpenStreetMap Foundation's Nominatim Usage Policy (1 request/second application-wide). Privacy: OSM Foundation Privacy Policy. - Project OSRM routing (OpenStreetMap mode only) — driving-distance and travel-time queries are sent to
router.project-osrm.org. Service: Project OSRM. Terms / project home: Project OSRM on GitHub. Privacy: the OSRM public router is operated by the OSRM community on a best-effort basis; please review the operator notice linked on the OSRM project page. - MapTiler — map tiles and geocoding calls go to
api.maptiler.com. Service: MapTiler. Terms: MapTiler Terms of Service. Privacy: MapTiler Privacy Policy. - Geoapify — tiles, geocoding and routing calls go to
api.geoapify.comandmaps.geoapify.com. Service: Geoapify. Terms: Geoapify Terms and Conditions. Privacy: Geoapify Privacy Policy.
安装:
- Install and activate WooCommerce first.
- Upload the plugin files to
/wp-content/plugins/routemile-woocommerce, or install through the WordPress plugins screen. - Go to WooCommerce → Settings → RouteMile and pick a map provider (see Configuration below for getting API keys).
- Set your restaurant location on the map, delivery radius, and delivery fee settings.
- Enable the RouteMile Delivery method in your shipping zone(s), or let the plugin add it automatically.
- Create users with the "Delivery Boy" role — their mobile app lives at the Delivery Dashboard link on their profile menu.
屏幕截图:
常见问题:
Do I need a Google Maps API key?
No. Pick the OpenStreetMap provider and the plugin uses bundled Leaflet plus free OSM tiles and Nominatim geocoding. Use Google Maps if you prefer its data quality and already have a key.
How is the delivery fee calculated?
From the straight-line (haversine) distance between your restaurant coordinates and the customer's dropped pin. You choose flat, per-km, or tiered pricing, and can set a minimum order amount and a free-delivery threshold.
Does it work with HPOS (high-performance order storage)?
Yes. RouteMile declares full HPOS compatibility and reads/writes order data only through WooCommerce CRUD APIs.
Which payment methods work?
All of them. RouteMile handles fulfilment, not payment. For cash on delivery it additionally tracks how much each rider has collected and pending hand-over.
Are my API keys safe?
Keys are stored in your own WordPress database, never sent anywhere except the map provider they belong to, and never printed in frontend JavaScript data (only in the map-provider URLs that require them). Restricting keys to your domain/server IP as described under Security Recommendations closes the remaining abuse vector.
Can customers see the rider's contact details?
Only after you assign a rider to their order, and only the rider's name and phone number, on the order-tracking page.
Where do riders get the app?
It is not a separate download. A rider logs into your site, opens the Delivery Dashboard page, and uses "Add to Home Screen" in their browser to install it as a PWA.
更新日志:
1.6.4
- Fixed classic checkout stuck on "No shipping options available" after the pin: the pin is now stamped onto the shipping package so WooCommerce's package-hash rate cache busts on every pin move (toast and totals always agree).
- Map honesty: fixed non-draggable restaurant marker on both pickers; coverage circle drawn at radius ÷ road-factor (exact for estimate providers, conservative guide for true-road ones); out-of-zone rejections name the by-road distance and range.
- Classic thank-you page restyled (was unstyled with giant tracking icons); block checkout works under classic themes (Astra, Storefront) via a the_content fallback.
- Checkout field registration moved to woocommerce_init (WC 11 timing), disallowed placeholder attributes removed; extension totals refresh retries once on transient failure.
- Docs: fixed dead Project OSRM Terms URL; WC tested up to 11.1.
- Plugin Directory review fix (round 3): the two remaining "escape late" outputs are now wrapped in
wp_kses_post()— thewoocommerce_my_account_my_address_descriptionfilter result in the My Account address template and thewc_get_email_order_items()result in the order-status email. Both keep their WooCommerce semantics (legitimate filtered HTML passes, dangerous markup is stripped). - Fixed: an undefined
$ivariable in the order-status email's totals rows (a PHP 8 warning under WP_DEBUG); the first totals row's thicker top border now renders as intended.
- Plugin Directory review fixes: corrected 3 invalid external-service URLs in the readme (Nominatim, MapTiler, Geoapify); removed the duplicate "Tested up to" header from the main plugin PHP file (kept only in readme.txt); replaced the dynamic-label
_n_noop()call in the order status registration (admin-configurable labels can't be in the .pot file, so the standard WP pattern is to droplabel_countfor custom statuses — our own deliveries dashboard renders per-status counts separately); and wrapped the 25 inline-SVG icon echoes withwp_kses_post()via a newroutew_agent_icon_e()helper so Plugin Check's escaping audit passes.
- Security: manual "completed" transitions are now gated on payment state. Previously a shop manager could mark an unpaid order completed from the deliveries dashboard, and an assigned delivery rider could do the same through the rider app on prepaid (bank-transfer/cheque) orders — WooCommerce records any completed order as paid, so two button taps created a "paid" order with no payment and no transaction record. Gateway-paid orders, cash-on-delivery with confirmed cash collection, and zero-total orders are unaffected.
- Internal: new regression suite (PG1) guards the payment gate on all four transition paths and fails the build if any future action can set completed on an unpaid order.
- Mile Zero design system: every customer and rider surface (checkout, order tracking, order-received, My Account, delivery-rider app) rebuilt on a fast, self-contained design system with bundled fonts — no more theme conflicts from generic Bootstrap styling.
- Order stage labels: rename the five delivery stages (label, colour, icon) from the settings screen; renames apply everywhere instantly and never touch stored order data.
- Brand colour: pick one colour and the whole plugin UI recolours, including the rider app's PWA theme; text contrast is checked automatically.
- Manager "Accept Order" action for newly placed orders; rider actions update the app in place with no page reloads; cash settlement banners update live.
- WordPress Plugin Check compliance: zero errors and warnings on the shipped zip.
- Plugin renamed to "RouteMile for WooCommerce" (plugin slug
routemile-woocommerce) — distinct from the existing commercial "FoodXpress" food-ordering plugin per the WP.org review feedback. - WP.org plugin-directory compliance: text domain unified to the plugin slug; inline script/style extracted to external files;
[order_number]in the receipt title now escaped (defence against merchant-controlled sequential-order-number formats); explicit capability check added to all admin-side data-migration paths; menu moved under the WooCommerce top-level (was a top-level item at a high position); map-provider "Powered by ..." credit is now an opt-in checkbox; readme's privacy section links each provider's Terms of Service and Privacy Policy and discloses Project OSRM. - One-time data migration copies every old
fxw_*option, transient, post meta, user meta, andwc-fxw-*order status to the newroutew_*keys on upgrade. Existing 1.4.x stores keep their settings, rider assignments, order statuses, and stored delivery addresses.
- Customer My Account dashboard overhaul.
- Delivery-rider PWA: installable app, live auto-refreshing order list, COD collection totals and settlement workflow with manager approval.
- Settings redesigned for non-technical admins: fields appear based on the selected map provider and fee mode; masked API-key input; clearer opening-hours controls ("open all day", special-occasion override).
- Kitchen notes now visible only to managers/admins; riders see delivery instructions only.
- Fixed: admin-bar open/close toggle, weekly-hours saving, receipt printing, unassign crash, and more — see CHANGELOG.md.
- Address deduplication on receipts and order screens; one-time migration normalises existing orders; free-delivery rates labelled clearly. Earlier releases: see CHANGELOG.md in the repository.