Orders and statuses
An order placed in the mobile app is created automatically in your WooCommerce shop. From there the order lives in the shop as usual, while its status and payment synchronise with the app both ways. In the Mappings section you set how the app's order data maps onto WooCommerce order fields.
How to open it
In the WordPress admin panel open WooCommerce, Settings, Integrations, MobiusApp, and scroll to the Mappings section. The section is only available after connecting.
What you can configure
- The mapping of app and WooCommerce order statuses
- The mapping of delivery methods
- The mapping of payment methods
- The mapping of customer fields, separately for individuals and legal entities
Mapping statuses, delivery and payment
For app orders to land in the shop correctly and for changes to travel back, fill in three tables. In each row the app value is on the left and the WooCommerce counterpart on the right.
- Order statuses: an app status against a WooCommerce order status. Filling it in matters: a status change only goes to the app for statuses mapped in this table.
- Delivery methods: an app delivery method against a WooCommerce delivery method.
- Payment methods: an app payment method against a WooCommerce payment gateway.
The app values in these tables come from the lists loaded from mobiusapp. If the lists are out of date, refresh them with "Refresh directories" in the Connection block.
Mapping customer fields
The app's customer data is mapped onto WooCommerce order fields. The mapping is set separately for individuals and for legal entities, in the Individual and Legal entity tables.
The app fields:
- First name and surname
- Phone
- Address
- City or town
- Company (for a legal entity)
- Company tax and registration numbers (for a legal entity)
For each app field choose a WooCommerce order field. Sensible defaults are set already: the first name and surname go to the billing name, the phone, email and address to the matching billing fields, and the company numbers to separate order fields. Change the mapping where needed, or choose not to transfer a field.
How it works
An order from the app
When a shopper places an order in the app, the plugin creates an order in WooCommerce: it matches products against the catalogue, fills in the customer data by the configured mapping and sets the delivery and payment. Every integration order is placed on a single service customer, which makes app orders easy to tell apart.
Status and payment changes
- The shopper paid in the app: the order in the shop is marked paid.
- The order was cancelled in the app: the order in the shop is cancelled.
- You changed the status or marked payment in the shop: the change goes to the app (if the status is mapped in the table).
Changes from the shop reach the app whichever way the order was edited: through the admin panel, an import or another plugin. Echo is ruled out: a change that came from the app is not sent back to the app.
Scenarios
Set up order intake
- Fill in the status, delivery and payment mappings.
- Map the customer fields, separately for individuals and legal entities.
- Press "Save changes".
Statuses do not reach the app
- Open the "Order statuses" table.
- Make sure the WooCommerce status you need is mapped to an app status. Without a mapping the change does not travel.
Limits and caveats
- If a WooCommerce status is not mapped in the status table, its change will not reach the app (this is recorded in the log).
- If a delivery or payment method is not mapped, the order is created with the delivery and payment data from the app but without a link to a particular WooCommerce method.
- Redeemed bonuses are kept in an order note and the shopper's comment in the customer note.
- The delivery price comes from the app order and is not recalculated by the shop.
- The town from the app is written into the order city; WooCommerce countries and regions have no town directory.
Orders from the app arrive at the order intake address the plugin registered on
connection (the admin-ajax.php entry point, independent of permalink settings).
Every notification is signed and verified against the secret; repeated deliveries
are recognised and do not create a duplicate. The order is created through the
WooCommerce CRUD (compatible with high-performance order storage, HPOS) on the
service customer. The reverse synchronisation runs on the standard WooCommerce
status and payment events, and sending happens in the background through the
action scheduler; there is loop protection.