WooCommerce
The WooCommerce integration brings orders from your WordPress store into Ritevo. You connect it with REST API keys generated in the WooCommerce panel. Because WooCommerce stores differ in their plugins, you set yourself how statuses, payment methods and plugin-added fields (tax id, pickup point) are read in Ritevo.
The same WooCommerce store can be connected only once. When you add it again, Ritevo refreshes the existing integration and turns it back on, even if it was deleted.
How to generate the API key
You create the keys in your store's WordPress panel. Copy both right away - you will paste them into Ritevo when adding the integration.
- Sign in to the WordPress panel and in the left menu choose WooCommerce, then Settings.
- Open the Advanced tab, then REST API. Click Add key.
- In the Description field enter any name, for example "Ritevo". In the User field pick the store's administrator account.
- In the Permissions field choose Read/Write - the highest available - and click Generate API key.
- Copy the Consumer key and the Consumer secret.
Connecting the account
Start in Ritevo:
- Go to Integrations in the left panel and click Add integration in the top right corner.
- In the Online stores section pick the WooCommerce tile.
- In the Account name field enter your own name for the integration, for example the store's name.
- In the Store address field enter the store's full address with
https://, without a trailing slash and without/wp-admin- for examplehttps://mystore.com. - In the Consumer Key and Consumer Secret fields paste the keys from the WooCommerce panel.
- Click Add integration. Ritevo connects to the store right away and checks the details: if they are valid, the integration is added and its settings open. If not - you will see the error returned by the store and nothing is saved.



Integration settings
After connecting, the integration is Active, but order fetching is off - you turn it on yourself. On the integration page you will find:
- Account name - your own name for this integration, for example the store's name. You can change it at any time.
- Store address - the address given when adding. It cannot be changed here; a new address or new keys go through Update credentials.
- Fetch orders - once on, Ritevo checks for new and changed orders about every 10 minutes. The rules shared by all channels: Fetching orders.
- Order status mapping, Payment method mapping and Advanced mapping - described below.

Mapping statuses and payments
Every store names its order statuses and payment methods its own way, so with online stores you decide yourself how they translate to Ritevo statuses and methods. You set the mapping once, on the integration page, and it applies to every order fetched from then on.
Order status mapping
Ritevo reads the status list from your store, including statuses added by plugins, so you see them under the same names as in the WooCommerce panel. Up front the standard WooCommerce statuses are assigned. You assign yourself the statuses added by plugins. The starting assignment:
- Confirmed - Processing, Completed, Refunded. A refunded order was a real sale, so it stays confirmed - you settle the refund separately.
- Cancelled - Cancelled.
- Awaiting payment - Pending payment, Failed.
- Awaiting confirmation - On hold.
One Ritevo status can have several store statuses assigned, but one store status only one Ritevo status. An order with a status you have not assigned anywhere arrives as Awaiting confirmation - you will see it and decide what to do.
Payment method mapping
Ritevo reads the method list from the payment gateways enabled in your store. Up front the methods built into WooCommerce are assigned. You assign yourself plugin gateways (Stripe, PayPal, Klarna and others), because every store has different ones. The starting assignment:
- Bank transfer - Direct bank transfer, Check payments.
- Cash on delivery - Cash on delivery.
A payment made with a method you have not assigned anywhere arrives as Other.

Advanced mapping - plugin fields
WooCommerce has no standard fields for a tax id, an invoice request or a pickup point - plugins add them, each under its own field name. In this card you point to the order field Ritevo should read each of these from. Up front the field names of popular plugins are filled in. You add yourself the field names of other plugins and remove the ones you do not need.
- Tax id / VAT number - the field with the buyer's tax id. When it has a value, the order gets the company details and the number for the invoice.
- Invoice request - the field Ritevo reads to tell whether the buyer wants an invoice. Only the value in the field matters: if it is "0", "no", "false" or "off", there is no request; any other value (for example "1", "yes", "true") is a request. When the field is empty, an invoice is requested whenever the buyer gave a tax id.
- Pickup point id - the field with the locker or point code (for example
WAW123). - Pickup point name and Pickup point description - the fields with the point's name and address, if the plugin stores them.
- Pickup point country - usually stays empty; Ritevo then takes the country from the delivery address.
You will find the field name in the plugin's settings or in the details of a test order. Enter it exactly - letter case and the leading underscore matter. One field can hold several names (for example after switching plugins): Ritevo uses the first one that has a value in the order.

What this integration gives you
- Orders - new and changed WooCommerce orders land in the orders table, with the buyer's details, invoice details, delivery (including the plugin's pickup point) and line items with product images.
Orders from WooCommerce
Ritevo fetches the whole WooCommerce order: the buyer, billing and shipping address, shipping method, payment, line items with gross prices and product images. An order changed in the store (for example a new status) is fetched again.
- Statuses and payments - translated according to your mapping, described above.
- Invoice - the company details and tax id are read from the fields set in Advanced mapping; with neither a company name nor a tax id the order has no invoice details. The invoice request follows the Invoice request field and gives the Customer asks for an invoice flag.
- Pickup point - the point's code and name are read from the fields set in Advanced mapping; without them the order has only the delivery address.
- Buyer's note - the order note typed at checkout goes into the order as the buyer's message.
- Additional services - supported. Fees the shop added to the order, for example for gift wrapping or carry-in, show up as separate line items for the whole order. A discount added as a fee shows up with a negative amount. More about additional services.
- Guest checkout - a guest order is fetched normally; the buyer then has no store customer id.
Reconnection required
This state appears when the store stopped accepting the credentials - the key was deleted in the store's panel, lost its permissions, or the store address changed. Until you provide new details, Ritevo neither fetches nor sends any data from that store.
- Generate new keys in the store's panel - the same way as when connecting for the first time.
- On the integration page in Ritevo click Update credentials, enter the store address and the new keys and confirm. Ritevo checks them with the store just like when adding - wrong details return an error, valid ones refresh the connection. The mappings, fetching settings and history stay unchanged.
Deleting the integration
Delete integration turns the integration off in Ritevo: it stops fetching and sending data, but what it fetched earlier stays. Restore integration turns it back on.
What the integration does not do
- It does not manage listings: it does not list, change prices or stock in WooCommerce.
- It does not fetch messages - WooCommerce has no buyer inbox. Customers write by email, so add an email integration for the store's mailbox.
- It sends nothing back to WooCommerce: when you change an order's status, create a shipment or issue an invoice in Ritevo, the order in WooCommerce stays unchanged.