New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | WooCommerce POS for iPhone, iPad & Android. Tap to Pay, Stripe Terminal, offline mode, multi-outlet stock — every WooCommerce payment gateway. | You have to log in to add a translation. | Details |
Original untranslated
WooCommerce POS for iPhone, iPad & Android. Tap to Pay, Stripe Terminal, offline mode, multi-outlet stock — every WooCommerce payment gateway.
You have to log in to edit this translation. |
|||
| ↑ | Oliver POS – WooCommerce POS for iPhone, iPad & Android | You have to log in to add a translation. | Details |
Original untranslated
Oliver POS – WooCommerce POS for iPhone, iPad & Android
CommentPlugin name. You have to log in to edit this translation. |
|||
| The <code>/.well-known/jwks.json</code> endpoint is the RSA public-key directory the plugin reads (no shop data sent in the request) to verify Phoenix-issued bearer tokens presented by the Oliver POS web register at <code>app.oliverpos.com</code>. The response is a small JSON document of public keys, cached on the merchant's site for 24 hours, and contains no merchant data. Required only on sites whose merchants use the web register; native iOS / Android apps continue to authenticate with WooCommerce consumer keys and never trigger this lookup. | You have to log in to add a translation. | Details | |
Original untranslated
The <code>/.well-known/jwks.json</code> endpoint is the RSA public-key directory the plugin reads (no shop data sent in the request) to verify Phoenix-issued bearer tokens presented by the Oliver POS web register at <code>app.oliverpos.com</code>. The response is a small JSON document of public keys, cached on the merchant's site for 24 hours, and contains no merchant data. Required only on sites whose merchants use the web register; native iOS / Android apps continue to authenticate with WooCommerce consumer keys and never trigger this lookup.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| Endpoints used: <code>/api/auth/token</code>, <code>/api/auth/register</code>, <code>/api/auth/claim</code>, <code>/api/subscriptions/current</code>, <code>/api/subscriptions/manage-link</code>, <code>/api/subscriptions/resync</code>, <code>/api/connect/status</code>, <code>/api/connect/accounts</code>, <code>/api/connect/sessions</code>, <code>/api/terminal/locations</code>, <code>/api/terminal/locations/sync</code>, <code>/api/devices/pairing-codes</code>, <code>/.well-known/jwks.json</code>. | You have to log in to add a translation. | Details | |
Original untranslated
Endpoints used: <code>/api/auth/token</code>, <code>/api/auth/register</code>, <code>/api/auth/claim</code>, <code>/api/subscriptions/current</code>, <code>/api/subscriptions/manage-link</code>, <code>/api/subscriptions/resync</code>, <code>/api/connect/status</code>, <code>/api/connect/accounts</code>, <code>/api/connect/sessions</code>, <code>/api/terminal/locations</code>, <code>/api/terminal/locations/sync</code>, <code>/api/devices/pairing-codes</code>, <code>/.well-known/jwks.json</code>.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| When it is sent: only after the merchant explicitly opts in by clicking <strong>"Create your free Oliver POS account"</strong> on the Billing page or on the first-run Dashboard onboarding panel (or <strong>"Connect with Stripe"</strong> on the Oliver Pay page), after which the page also fetches the current subscription status, and on subsequent merchant actions: clicking "Manage your current plan" on Billing, pasting an OPAY-XXXX-XXXX-XXXX activation code into the Billing page (or following the marketing-site deep link <code>?claim=OPAY-…</code>), adding / editing / deleting an outlet, running the "Sync Terminal Locations" / "Refresh status" / "Test connection" / "Refresh plan from Stripe" actions, or when a paired Oliver POS device requests a Phoenix pairing code via <code>POST /oliver-pos/v1/devices/phoenix-pair-code</code> (which the plugin proxies through to <code>/api/devices/pairing-codes</code>). Plan selection itself happens on <a href="proxy.php?url=https%3A%2F%2Foliverpos.com%2Fpricing">oliverpos.com/pricing</a>, not inside wp-admin. No outbound call is made on plugin activation, on <code>plugins_loaded</code>, on <code>init</code>, on the Oliver POS Dashboard / Settings / Reports / Staff / Outlets / Receipts admin pages (the Dashboard onboarding panel only transmits when the explicit "Create your free Oliver POS account" button is clicked — its disclosure expander lists exactly what gets sent), or on any frontend request. | You have to log in to add a translation. | Details | |
Original untranslated
When it is sent: only after the merchant explicitly opts in by clicking <strong>"Create your free Oliver POS account"</strong> on the Billing page or on the first-run Dashboard onboarding panel (or <strong>"Connect with Stripe"</strong> on the Oliver Pay page), after which the page also fetches the current subscription status, and on subsequent merchant actions: clicking "Manage your current plan" on Billing, pasting an OPAY-XXXX-XXXX-XXXX activation code into the Billing page (or following the marketing-site deep link <code>?claim=OPAY-…</code>), adding / editing / deleting an outlet, running the "Sync Terminal Locations" / "Refresh status" / "Test connection" / "Refresh plan from Stripe" actions, or when a paired Oliver POS device requests a Phoenix pairing code via <code>POST /oliver-pos/v1/devices/phoenix-pair-code</code> (which the plugin proxies through to <code>/api/devices/pairing-codes</code>). Plan selection itself happens on <a href="proxy.php?url=https%3A%2F%2Foliverpos.com%2Fpricing">oliverpos.com/pricing</a>, not inside wp-admin. No outbound call is made on plugin activation, on <code>plugins_loaded</code>, on <code>init</code>, on the Oliver POS Dashboard / Settings / Reports / Staff / Outlets / Receipts admin pages (the Dashboard onboarding panel only transmits when the explicit "Create your free Oliver POS account" button is clicked — its disclosure expander lists exactly what gets sent), or on any frontend request.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| Yes. Because Oliver POS reads and writes through the official WooCommerce REST API, your existing WooCommerce extensions keep working at the counter — including WooCommerce Subscriptions, Memberships, Bookings, Product Bundles, Points & Rewards, Gift Cards and WooPayments. There is no bespoke integration to install per plugin, and the customer experience on your online store stays unchanged. | You have to log in to add a translation. | Details | |
Original untranslated
Yes. Because Oliver POS reads and writes through the official WooCommerce REST API, your existing WooCommerce extensions keep working at the counter — including WooCommerce Subscriptions, Memberships, Bookings, Product Bundles, Points & Rewards, Gift Cards and WooPayments. There is no bespoke integration to install per plugin, and the customer experience on your online store stays unchanged.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Yes. Oliver POS supports <strong>Tap to Pay on iPhone</strong> (iOS 16.4+) and <strong>Tap to Pay on Android</strong> through our integration with Stripe Terminal. Tap a contactless card, Apple Pay or Google Pay against the back of the phone, the charge runs through your own Stripe account, and the completed payment is recorded on the WooCommerce order — no extra reader, no double entry, no reconciliation drift. | You have to log in to add a translation. | Details | |
Original untranslated
Yes. Oliver POS supports <strong>Tap to Pay on iPhone</strong> (iOS 16.4+) and <strong>Tap to Pay on Android</strong> through our integration with Stripe Terminal. Tap a contactless card, Apple Pay or Google Pay against the back of the phone, the charge runs through your own Stripe account, and the completed payment is recorded on the WooCommerce order — no extra reader, no double entry, no reconciliation drift.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Yes. Any USB or Bluetooth barcode scanner that emulates a keyboard works out of the box. Add the barcode as the SKU or to a custom field in WooCommerce, and Oliver POS will look it up at the speed of the scanner. You can also scan barcodes with the device's built-in camera on iPhone, iPad and Android — no extra hardware required. | You have to log in to add a translation. | Details | |
Original untranslated
Yes. Any USB or Bluetooth barcode scanner that emulates a keyboard works out of the box. Add the barcode as the SKU or to a custom field in WooCommerce, and Oliver POS will look it up at the speed of the scanner. You can also scan barcodes with the device's built-in camera on iPhone, iPad and Android — no extra hardware required.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Yes — thermal, inkjet, laser and Bluetooth receipt printers all work. The Oliver POS terminals ship with an integrated thermal printer that auto-prints after every checkout. Other setups print to whatever printer is connected as the device default. Email and SMS receipts are also supported. | You have to log in to add a translation. | Details | |
Original untranslated
Yes — thermal, inkjet, laser and Bluetooth receipt printers all work. The Oliver POS terminals ship with an integrated thermal printer that auto-prints after every checkout. Other setups print to whatever printer is connected as the device default. Email and SMS receipts are also supported.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| For GDPR, the plugin transmits only the data documented in the <strong>External services</strong> section below, never sells data, never runs third-party analytics, and removes all stored Oliver POS data cleanly on uninstall. | You have to log in to add a translation. | Details | |
Original untranslated
For GDPR, the plugin transmits only the data documented in the <strong>External services</strong> section below, never sells data, never runs third-party analytics, and removes all stored Oliver POS data cleanly on uninstall.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Card data never touches the Oliver POS plugin or our servers. For integrated card payments via Stripe Terminal or any WooCommerce gateway, card information flows directly between the customer's card / terminal / browser and the gateway, keeping your shop's PCI scope to the SAQ-A or SAQ-A-EP minimum. | You have to log in to add a translation. | Details | |
Original untranslated
Card data never touches the Oliver POS plugin or our servers. For integrated card payments via Stripe Terminal or any WooCommerce gateway, card information flows directly between the customer's card / terminal / browser and the gateway, keeping your shop's PCI scope to the SAQ-A or SAQ-A-EP minimum.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Yes. When you pair a device, Oliver POS mints a real WooCommerce REST API key for that station and the device speaks <code>wp-json/wc/v3/*</code> directly. Your orders, products, refunds and customers are stored as standard WooCommerce records — no proprietary tables, no vendor lock-in. If you ever stop using Oliver POS, your data stays exactly where it is. | You have to log in to add a translation. | Details | |
Original untranslated
Yes. When you pair a device, Oliver POS mints a real WooCommerce REST API key for that station and the device speaks <code>wp-json/wc/v3/*</code> directly. Your orders, products, refunds and customers are stored as standard WooCommerce records — no proprietary tables, no vendor lock-in. If you ever stop using Oliver POS, your data stays exactly where it is.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Oliver POS offers a free plan with no credit card required. Paid tiers add multi-outlet, advanced reporting, integrated payments and priority support. See <a href="proxy.php?url=https%3A%2F%2Foliverpos.com%2Fpricing%3Futm_source%3Dwordpress.org%26amp%3Bamp%3Butm_medium%3Dplugin%26amp%3Bamp%3Butm_campaign%3Dreadme%26amp%3Bamp%3Butm_content%3Dpricing-faq">current pricing</a> on oliverpos.com. | You have to log in to add a translation. | Details | |
Original untranslated
Oliver POS offers a free plan with no credit card required. Paid tiers add multi-outlet, advanced reporting, integrated payments and priority support. See <a href="proxy.php?url=https%3A%2F%2Foliverpos.com%2Fpricing%3Futm_source%3Dwordpress.org%26amp%3Bamp%3Butm_medium%3Dplugin%26amp%3Bamp%3Butm_campaign%3Dreadme%26amp%3Bamp%3Butm_content%3Dpricing-faq">current pricing</a> on oliverpos.com.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| We've shipped Oliver POS to over 45,000 retailers, and the median setup is under three minutes: | You have to log in to add a translation. | Details | |
Original untranslated
We've shipped Oliver POS to over 45,000 retailers, and the median setup is under three minutes:
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Yes. Oliver POS is built around outlets — each physical store or pop-up gets its own stock levels, register sequence, payment methods, tax setup and timezone, while all rolling up to the same WooCommerce shop. Stock can be transferred between outlets, and reports can be filtered per outlet, per register or globally. | You have to log in to add a translation. | Details | |
Original untranslated
Yes. Oliver POS is built around outlets — each physical store or pop-up gets its own stock levels, register sequence, payment methods, tax setup and timezone, while all rolling up to the same WooCommerce shop. Stock can be transferred between outlets, and reports can be filtered per outlet, per register or globally.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
Export as
Comment
Short description.