Connect your WooCommerce store
Connect an existing WordPress store to FlintPOS. Choose which system owns the product list before you sync. Then check products, prices, photos, and stock in both places.
Where to find it
Admins open Settings > WooCommerce in the Website & Integrations group. The tab appears when the WooCommerce integration is enabled.
Product locationSettings > WooCommerce
Before you start
Have the WordPress site URL and WooCommerce REST API consumer key and secret ready. Create the sign-in details in WordPress with the access level needed by the chosen direction. Run the connection test before importing or pushing products.
Steps to follow
- Enter the Site URL, Consumer Key, and Consumer Secret. Then select Test Connection.
- Choose the source policy. Select POS is source when FlintPOS owns product names, prices, categories, photos, and stock, or WooCommerce is source when WordPress owns the catalog and FlintPOS imports it.
- For POS as source, choose the product, photo, category, deletion, and stock-only sync switches.
- For WooCommerce as source, use Import All Products from WooCommerce for initial setup. Products match by SKU first. New products are created in FlintPOS and POS-only products are not deleted.
- For POS as source, use Push All Products to WooCommerce after reviewing the source policy. Existing products are updated, matching by SKU first.
- Save the settings. Then test one product edit and one stock change before enabling broad automatic sync.
Choose one catalog owner
Choose POS is source when FlintPOS owns product data. It can send selected changes to WooCommerce. Choose WooCommerce is source when WordPress owns product data; import its products into FlintPOS. For example, when WordPress owns prices, a POS price edit will not update the website. Stock-only mode sends inventory counts from POS. It leaves WooCommerce names, prices, descriptions, categories, and photos as they are.
Same SKUs help FlintPOS match products. Without a matching SKU, a sync may create a new product instead of updating one. Test one item in both systems before a large sync.
Fields and choices
| Field | Guidance |
|---|---|
| POS is source | FlintPOS owns catalog changes and can mirror chosen changes to WooCommerce. |
| WooCommerce is source | WordPress owns catalog changes. Import them into FlintPOS when needed and do not expect POS edits to push back. |
| Product / Photo / Category Sync | Controls which POS changes are sent when POS is the source. |
| Deletion Sync | Removes or archives the matching WooCommerce product when the POS product is deleted or archived. Enable only after review. |
| Stock-only Sync | Pushes inventory counts while leaving WooCommerce names, prices, descriptions, categories, and images alone. |
| Consumer credentials | Keep the key and secret in the integration fields and rotate them in WordPress if exposed. |
Check the result
The connection test shows the store version and product count. Review which records were created, changed, skipped, or failed. Check a product and its stock in both systems before you rely on automatic sync.
Troubleshooting
- If the connection test fails, check the site URL, HTTPS, REST API key permissions, and secret. Then save and test again.
- If products duplicate, confirm SKUs match and that only one system is being treated as the source.
- If stock changes but catalog fields do not, review the stock-only switch and source policy.
- If an import skips variable products, review the displayed result. The current import does not create every variable-product shape.