WooCommerce is managed inside Admin → Integrations. The Integrations item uses the Plug Zap icon; the WooCommerce tab and page use the Shopping Cart icon. This screen changes real catalog, stock, checkout, payment-reporting, and imported-sale behavior, so test with one controlled product and order before a broad sync.

Before you beginUse an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.

Step by step

  1. Open Admin → Integrations, then choose WooCommerce. If you start on the Integrations overview, select Manage WooCommerce on its Shopping Cart card.
  2. In Connection, enter the complete Store URL and choose Connect with WooCommerce. Approve the connection on the Woo site and return to CentriPOS. Use Test connection to confirm the saved authorization.
  3. Use Manual REST API credentials only when the normal authorization flow is not suitable. Enter both Consumer key and Consumer secret, test them, and keep the secret private. A successful test before the first save does not enable sync by itself.
  4. Turn Integration enabled on only when the intended store and tenant are confirmed. Under Sync options, independently choose Products, Inventory, and Orders, then select Save at the top of the page. Products pushes the POS catalog to Woo; Inventory keeps stock levels synchronized; Orders pulls Woo orders into CentriPOS as sales.
  5. In Product links, choose Scan Woo products to review up to the recent Woo products returned by the audit. Each row shows Linked or Woo only, its Woo ID, SKU or variation SKUs, publication status, and any proposed SKU, variation-SKU, or title match.
  6. Review every proposed match before choosing Link product. Link matching SKUs applies eligible matches in bulk and reports how many linked, matched, and skipped. Linking writes the CentriPOS product ID into Woo product metadata; matching by title is a fallback, not proof that two products are the same.
  7. In Order register, select a CentriPOS Location and an active Register at that location, then choose Save register. Imported Woo sales, sales reporting, and register-level NMI Gateway overrides use this same register.
  8. Configure Checkout calculator only if the Woo cart or checkout plugin is prepared to call CentriPOS. Calculator enabled exposes the branded calculator endpoint; Fulfillment rates returns enabled pickup, delivery, and shipping choices; ZIPTax calculation calculates tax from the destination address.
  9. Generate the Shared secret once, store it securely in the Woo plugin, and send it using the x-centripos-woo-secret header. Rotating the secret invalidates the value previously configured in Woo, so update both sides together.
  10. Under CentriPOS payment gateway, enable Credit / debit card or Bank account / ACH only after the selected order register has the corresponding NMI e-cart capability. Card supports NMI tokenization and 3DS when enabled; ACH requires ACH on that register. The method IDs and checkout labels shown on this page are read-only.
  11. Copy the branded Payment endpoint into the compatible Woo payment bridge. The bridge tokenizes payment details rather than sending raw card or bank data to CentriPOS; do not replace the pos.getcentri.com endpoint with an internal service URL.
  12. In Payment types, choose Refresh after connecting the store or enabling a Woo checkout method. Map each Woo method to the CentriPOS payment type that should appear in sales and register reporting, then choose Save mappings. A method can also appear because it was seen on an imported order.
  13. Use Sync now for a deliberate manual operation: Push products, Sync inventory, Pull orders, or Refresh linked orders. Enterprise, Agency, and Platform tenants also see Push network inventory. Do not click several sync actions repeatedly while one is still running.
  14. After a sync, read the completion message and the Last product sync, Last inventory sync, and Last order sync timestamps. The linked-product count confirms mappings, but it does not prove every Woo item is linked or that every row synchronized without an error.
  15. Place one controlled Woo order using a linked SKU and a mapped payment method. Confirm it appears in CentriPOS sales under the selected location and register with the expected customer, items, fulfillment, tax, payment type, and Woo order reference. There is no separate Woo “Order Intake” queue on this integration page.
  16. If the business uses CentriPOS to return a Woo-origin sale, verify the original Woo reference and watch the refund-sync result. Do not retry a completed refund merely because Woo takes time to refresh; first confirm the CentriPOS receipt and integration status to avoid a duplicate operational action.

Screen and contract reference

Control or areaWhat it means
Integration enabledMaster switch for the saved WooCommerce integration. Turning it off pauses configured synchronization without deleting mappings.
Store URLThe public HTTPS address of the WooCommerce store being connected.
Connect with WooCommerceStarts the Woo authorization flow and returns to the CentriPOS WooCommerce settings page.
Manual REST API credentialsOptional Consumer key and Consumer secret fields for stores that cannot use the normal authorization flow. Both values are required together.
Test connection / Test credentialsChecks that CentriPOS can reach the store and identifies the connected WooCommerce version; it does not by itself enable synchronization.
ProductsPushes the CentriPOS product catalog to WooCommerce when product sync is enabled or manually run.
InventoryKeeps Woo stock levels synchronized from the applicable CentriPOS inventory scope.
OrdersPulls WooCommerce orders into CentriPOS as sales.
Product linksAudit of recent Woo products and their CentriPOS mapping state, Woo ID, SKU, variation SKUs, status, and proposed match.
Scan Woo productsRefreshes the product-link audit without linking anything.
Link productConnects one reviewed Woo product to the proposed CentriPOS product.
Link matching SKUsBulk-links eligible audited matches and reports linked, matched, and skipped counts. Review ambiguous or title-only matches individually.
Order registerThe location and active register used for imported Woo sales, their reporting scope, and register-level e-cart gateway overrides.
Calculator enabledAllows the compatible Woo plugin to call the CentriPOS checkout-calculation endpoint.
Fulfillment ratesExposes enabled pickup, delivery, and shipping methods to the Woo checkout calculator.
ZIPTax calculationCalculates checkout tax using the destination address.
Calculator endpointBranded pos.getcentri.com URL used by the compatible Woo cart or checkout plugin.
Shared secretAuthenticates checkout-calculator and payment-bridge calls. Generate or rotate it here, then store the same current value securely in Woo.
Credit / debit cardEnables the CentriPOS Woo method backed by the selected register’s NMI card configuration and optional 3DS.
Bank account / ACHEnables the CentriPOS Woo ACH method when ACH is configured on the selected register.
Payment endpointBranded pos.getcentri.com endpoint used by the compatible payment bridge after secure browser-side tokenization.
Payment typesMaps Woo checkout method IDs to enabled CentriPOS payment types used in imported sales and reporting.
Refresh payment methodsReloads methods enabled in Woo or discovered on orders.
Push productsRuns a catalog push immediately.
Sync inventoryRuns inventory synchronization immediately.
Push network inventoryEnterprise-level action for supported network tenants; it is not shown to every business.
Pull ordersPolls Woo and imports eligible orders into CentriPOS sales.
Refresh linked ordersRefreshes the CentriPOS records already mapped to Woo orders.
Last sync timestampsShow when product, inventory, and order sync last completed; Never means no successful timestamp has been recorded.
Linked products countNumber of saved CentriPOS-to-Woo product mappings, not a guarantee that the full catalogs are identical.

Expected result

The intended Woo store reports a healthy connection; the enabled product, inventory, and order directions match the operating plan; reviewed products are linked to the correct CentriPOS records; imported orders post once to the selected location and register with the mapped payment type; and any enabled calculator or payment bridge succeeds through the branded endpoint with the current shared secret.

Troubleshooting

  • Confirm you are changing the intended business and location before saving.
  • Record the previous setting when a change affects live selling, payments, tax, or integrations.
  • Use a controlled test record after saving before rolling the setting out broadly.

More guides

Build an itemized payment in MoneyUse Products or Amount & description to build one receipt, attach the customer, and follow the appropriate payment or service-estimate workflow.
Take a one-time payment in Virtual TerminalReview a one-time amount, tax and contact at the correct payment station, use its verified secure checkout, and recover the original receipt after an uncertain result.
Review booking payments, refunds and earned careKeep a booking’s customer payments, unused advances, completed care, cancellation fees and refunds distinct, then read a correctly scoped accrual report.
Configure booking properties and customer pagesSet accommodations, service packages, availability, required intake and payment terms, then review the correctly branded booking page before sharing it.