SellerCloud Integration

The SellerCloud integration syncs products, inventory, customers, and orders between SellerCloud and WizCommerce. The connection uses JWT token-based authentication via SellerCloud's API, with token refresh handled automatically so the connection stays live without manual intervention.

This article walks through how the integration is set up, what data syncs, and how to handle the common scenarios.

Table of Contents

Before You Begin

Ensure the following are configured on your side:

1. Base URL: Your SellerCloud API base endpoint.
2. Username: A dedicated SellerCloud account for the integration.
3. Password: The password for that account.

Share these with WizCommerce team through a secure channel, they are used to authenticate and generate the JWT access token.

A. How the Connection Works

WizCommerce sends a login request to SellerCloud using the configured username and password. SellerCloud returns a JWT access token, which is stored securely on the WizCommerce side and included in the Authorization: Bearer <access_token> header on every API request.

Tokens are automatically refreshed when they expire, so the connection stays live without manual intervention. Authentication failures are logged for monitoring.

B. What Data Syncs Between SellerCloud and WizCommerce

The integration between SellerCloud and WizCommerce keeps your data in sync across both platforms. Below is a quick overview of the entities that sync, the direction of the data flow, and what each covers. 

C. Sync Timing

Product, inventory, and customer pulls run on a schedule, fetching only records changed since the last sync. Confirmed WizCommerce orders push to SellerCloud shortly after order confirmation. For on-demand refresh, contact WizCommerce team or reach out to help@wizcommerce.com.

D. Troubleshooting and Common Issues

» A new product or SKU isn't showing in WizCommerce

• Confirm the product is set to active in SellerCloud (is_active = true). Inactive products are excluded.
• Wait for the next incremental sync. The integration uses the LastUpdatedFrom filter to fetch only changes since the last sync.
• If the product is still missing after the next sync, contact help@wizcommerce.com.

» A customer doesn't match between SellerCloud and WizCommerce

Customers sync both ways. Updates made in WizCommerce push to SellerCloud, and SellerCloud-origin updates pull into WizCommerce. If something looks off, confirm where the change was made and which side is the master for that field. If a customer's sales rep doesn't carry through correctly, confirm the sales rep mapping with WizCommerce team.

» Orders aren't pushing - authentication issue

If the JWT token has expired and refresh has failed, push attempts will fail until the connection re-authenticates. Authentication failures are logged on the WizCommerce side. Contact help@wizcommerce.com if pushes are persistently failing, support will check the auth logs.

» An order failed to push because the customer isn't in SellerCloud

Before an order can push, the customer must exist in SellerCloud. If the customer was created in WizCommerce and hasn't synced to SellerCloud yet, the order push will fail. Push the customer first, then retry the order.

» An order failed to push because of product mapping

If a product on the order line doesn't have a SellerCloud reference, the push will fail validation. Add the product in SellerCloud (and confirm the mapping in WizCommerce), then retry.

FAQs

1. Do I need to refresh my JWT token manually?

A. No. Tokens are refreshed automatically by the integration when they expire. You only need to act if authentication fails repeatedly — at that point, contact support.

2. Are inactive products synced?

A. Yes. WizCommerce pulls all products from SellerCloud, including inactive ones. Inactive products are synced to WizCommerce but kept in a deactivated state, they exist in the system but aren't active in your storefront or available for ordering until reactivated

3. How are products kept in sync efficiently?

A. Products are fetched in batches of 50 with pagination, and the integration uses the LastUpdatedFrom filter to pull only records changed since the last sync.