Delist and delete items
Delist first, then delete the Business Central item separately. Local offline flags and zero inventory do not prove that an external offer has been removed.
Activate protection once
Existing companies retain their previous deletion behavior until an administrator explicitly activates protection in Delist Requests. Update the Hub and the sales channels in use together. Review Audit Catalogue, stop publication jobs and resolve outstanding uploads and feeds before activation. Then resume the jobs.
Protection is activated per marketplace. The Protection by Marketplace action on Delist Requests shows for each marketplace whether its connector supports delisting and whether protection is active. Select the marketplace and choose Activate Protection. Only marketplaces whose connector supports delisting can be activated. Marketplaces without that support do not prevent activating the others; their listings are not delisted, and deleting such a row removes only the Business Central record, as before. Activate for All Marketplaces protects every marketplace of the company, including later ones, but requires every marketplace with listings to support delisting. An earlier company-wide activation continues to cover all marketplaces.
If an item is also listed on a supported marketplace that is not activated yet, delisting stops and names that marketplace; Open Protection by Marketplace takes you directly to the activation. A protected marketplace cannot be renamed, and listings cannot move to a marketplace without protection.
The publication freeze of an item or variant delisting applies to the marketplaces that were protected when the delisting started, including listings created there later. A marketplace whose protection you activate afterwards was not part of the delisting: its listings of this item stay publishable; remove them by delisting the listing itself.
Activation remains until an administrator deactivates protection for the marketplace (see below); retained requests and pending publications remain protected independently of licensing or channel activation. A copied company needs its own activation before starting new requests and cannot reuse copied deletion evidence.
Deactivate protection for a marketplace
From Hub 2.238: if a marketplace is no longer served or the seller account can no longer be reached, for example after a suspension, deactivate protection for that marketplace: open Protection by Marketplace, select the marketplace and choose Deactivate Protection. Only administrators can use this action.
This deletes all delisting requests, targets, attempts, evidence and publication journal entries of that marketplace, including open ones. A request with targets on other marketplaces keeps them. Afterwards the marketplace behaves as if protection had never been activated: deleting a listing again removes only the Business Central record. Offers that were still being delisted can remain on the marketplace and are no longer tracked. The activity log records who deactivated protection, when, and how many records were deleted.
If protection was active for all marketplaces, it is kept for each of the other existing marketplaces individually, with the original time; marketplaces added later are then no longer protected automatically. A paused automation stays paused.
Stop the publication jobs of that marketplace first and deactivate protection in a quiet period: with many targets the run locks the delisting tables until it ends, also for delisting on other marketplaces. If the delisting job is processing a target of that marketplace at that moment, deactivation is refused; try again after a few minutes. If the connector keeps delisting records of its own, protection can only be deactivated once the installed connector version supports removing them; until then a message names the marketplace.
You can activate protection again at any time. It then starts afresh: earlier delistings no longer cover this marketplace.
Start a request
- Choose Prepare Delisting on an item, variant, marketplace listing or additional offer. Review the proposed accounts, SKUs, product identities and relationships.
- Confirm the scope. Only confirmation saves the request and blocks further publication.
- Open Delist Requests and choose Set Up Delisting Job once. Existing schedules and deliberate holds are preserved. Process Due Targets runs one bounded batch immediately.
- Inspect Open Targets and Attempt History. Accepted HTTP calls and feed IDs remain Awaiting Confirmation until their outcome is verified.
- Once all targets are confirmed, use the normal Business Central delete action. Inventory, open sales documents, marketplace orders and BOM dependencies are still checked.
Opening the preview saves pending changes from the source page. Cancelling the preview retains these changes and creates no delisting request.
The item FactBox shows requests and open targets. The Hub monitor reports attention cases, overdue targets, unknown publication outcomes and a missing or stopped job. The item list action previews all selected items together and creates the requests atomically after confirmation. A changed identity rolls the whole batch back. Items need a request if they have listings or retained external associations. Other listing, offer and variant actions apply to the current row.
Variants, packs and FBA
An item request covers its listings, variants and additional offers. A variant request preserves siblings; an offer request freezes only that pack or fulfillment offer. A shared parent is removed only after its other members are resolved. Shared SKUs or product IDs outside the confirmed scope require review. A set keeps its components; deleting a component remains blocked while assembly or production BOMs reference it.
Shopware verifies the SKU – like Shopware itself, without distinguishing upper and lower case – and the saved product UUID. Replaced identities and products with remaining children are not deleted blindly. From Shopware 6 1.81 with Hub 2.236, the action Remove from Shop on a Shopware variant master delists its container together with its variants: one shared preview, then the variants first and the container afterwards. Amazon correlates seller, marketplace, SKU, feed and message, then verifies external absence after processing. It removes the seller offer, not the ASIN from Amazon's general catalogue.
FBA release additionally requires a recent inventory sync proving that available, reserved, inbound, unfulfillable and processing quantities are zero. This is checked again at final BC deletion. No disposal or removal order is created.
Resolve uncertain outcomes
Publication Journal retains product writes before HTTP. A timeout may hide an accepted write. Such reservations never expire into success. Shopware 6 (from 1.81) settles an entry 60 minutes after sending, because the shop provably can no longer carry out the write after that; a write the shop accepted for later execution (HTTP 202) stays open. Settled entries – their outcome is proven – are deleted by the nightly data protection run 90 days after they were settled; the activity log shows how many. Open entries stay regardless of their age, and the delisting protection stays active once enabled, even with an empty journal. Known Amazon feeds are polled to a terminal state. If an asynchronous deletion may have been sent but its feed ID is missing, even a later absent listing cannot release the request. An administrator must reconcile the exact external operation using the channel's feed history or server logs. Until it is reliably resolved, the protection remains in place.
After fixing a known configuration or transient failure, use Check Again. Cancel Unsent Request is available only without an active worker, submitted deletion or confirmed target; a failed preflight alone does not prevent cancellation. Cancellation does not send a republication.
Reconcile Known Operation verifies an existing feed ID against its original environment, seller, marketplace and feed type. If a local crash lost its tracker, a recovered tracker exposes the processing report. Refresh listing statuses and quantities afterwards. The recovery does not reconstruct or confirm original sent values. An unknown outcome without a feed ID remains blocked.
Rollout
The additional sales channels require Hub 2.230. Existing Shopware 6 and Amazon channels require at least Shopware 6 1.75 and Amazon 1.111. The additional adapters have separate acceptance checks for Ariba 1.2, eBay 1.20, Kaufland 1.16 and Otto 1.18. Before activation, verify that the installed versions are approved and review all channel associations. Unsupported channels cannot be activated, and activation for all marketplaces fails while such a channel has listings or native associations. Activate the supported marketplaces individually instead.
- Ariba requires final evidence for the exact buyer and catalogue version. A downloaded CIF catalogue remains blocked until there is verifiable evidence from the portal or buyer. A shared replacement can omit selected rows and preserve the remaining rows. Use catalogue retirement when removing the last row. The catalogue history can discard a replacement that was never issued.
- eBay verifies the seller, marketplace, SKU and exact offer ID. Confirmation checks Inventory offers and active or scheduled Trading listings. Unresolved legacy associations require a documented reconciliation with the original seller account.
- Kaufland verifies the exact unit in the seller account and storefront. The shared product page remains in place. An accepted import requires the original import ID, the final processing result and proof that the unit is absent.
- Otto verifies the seller SKU, its active status and any outstanding product or availability tasks. An accepted status request still needs confirmation.
- Shopify remains blocked for Hub delisting. Native product or variant associations can block activation without a Hub listing and prevent BC deletion when protection is active. Full Shopify support requires Microsoft extension points before HTTP and for correlated final outcomes. The Hub cannot cover every native Microsoft publication path yet.
The delisting job user needs the Hub permission set and the required execution permissions for the installed connectors. A custom role must be able to run the mandatory subscribers of every installed delisting adapter. BC checks those permissions before the channel filter. A request remains blocked when permissions are missing.
Run Audit Catalogue before starting operations. It only reports inconsistent identities, orphan links, missing components and outstanding feeds. Review orphan rows before preparing targeted repair requests. No missing BC item triggers an automatic remote delete.
An orphan Shopware container can be prepared separately from the audit. Remote children and other local owners of the same shop SKU or product UUID prevent its deletion. Remove confirmed local listing mappings before deleting their container; dissolving a family must not re-publish delisted products.
Simulation provides no real-world deletion evidence. Copied requests from another company, environment or tenant are refused. This package does not automatically purge evidence, unresolved targets or publication reservations. Use dedicated external test listings for live acceptance tests.