On this page

WordPress and WooCommerce integration

Nviti supports website chat embedding and a separate linked-store connection for compatible WordPress/WooCommerce sites.

Add chat to WordPress

Create an active Chat Widget, copy its generated embed code, and add it to the intended WordPress pages. Follow WordPress Setup.

A widget key identifies customer chat. It is different from the private Store Token used for commerce synchronization.

Connect a linked store

Watch the linked-store connection and verification in the ecommerce course.

Connect a WooCommerce linked store Watch on YouTube from 00:08
  1. Open Shop → Linked Stores and select Create.
  2. Enter a name and select WordPress / WooCommerce.
  3. Set Store URL to the site's base URL, such as https://shop.example.com.
  4. Configure Active, Sync Products, and Sync Orders for the integration you need.
  5. Set the private Store Token and configure the same token in the compatible WordPress connector.
  6. Save, then use Test to check the connection.
  7. Use Pull Products to queue a catalogue import.

The WordPress site needs the compatible Nviti connector endpoints. A standard WordPress installation or chat embed alone does not expose them. Obtain the connector package and its installation instructions from the integration owner or Nviti support.

Monitor synchronization

Verify the linked store, imported products, and customer catalogue.

Pull products and verify the sync Watch on YouTube from 00:08

Review the linked store's Status, Last Synced At, and Last Error. A queued product pull is not confirmation that every product imported successfully. Review the catalogue after completion. Synchronization can remove local linked products that WooCommerce reports as trashed or deleted. Keep the source catalogue accurate and review deletions before pulling a large update.

The Sync Orders setting enables the relevant integration behavior; verify the supported order journey with a test order before relying on synchronization. See Orders.

Troubleshooting

If Test fails, check the base URL, connector installation, matching Store Token, and endpoint access. If products are missing, confirm the store is active and product sync is enabled, then review the recorded error.

Keep Store Tokens out of public page code and customer chat. After changing a token, update both sides and test again.