Replies: 1 comment
|
Hi, Great questions! To address both: The Sellbrite API is scoped to inventory management, product creation, and order fulfillment. So unfortunately, neither use case is supported programmatically at this time. Imports from BigCommerce can only be triggered manually through the Sellbrite dashboard, and there is no API or automation path to identify or clean up stale/ghost channel listing records. Opening a support case remains the only path for that cleanup, after which you can re-run the import manually. Happy to help if anything else comes up! Best, |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Team,
We are trying to clarify two separate BigCommerce/Sellbrite workflow questions.
First, for normal operations: we use Import From BigCommerce to create or refresh the BigCommerce channel listing links in Sellbrite. In normal cases, this correctly matches BigCommerce listings to existing Sellbrite products by SKU. We want to trigger that import programmatically so newly created BigCommerce listings can be linked in Sellbrite without a manual UI step, allowing Sellbrite inventory management to begin applying to those listings.
Is there any supported way to trigger Import From BigCommerce programmatically through an API endpoint, webhook, internal job trigger, or other supported automation path?
Second, for exception handling: we occasionally encounter stale or “ghost” BigCommerce channel listing records in Sellbrite. These are records Sellbrite still believes exist, but which no longer correspond to live BigCommerce listings, usually after products/listings were previously pruned. Our current support-assisted recovery path is for Sellbrite support to delete the affected stale BigCommerce channel listing records, after which we manually run Import From BigCommerce again.
Is there any supported API or automation path to identify, clear, or initiate cleanup of those stale/ghost BigCommerce channel listing records, or is opening a support case still the only supported recovery path?
Thank you!
All reactions