> ## Documentation Index > Fetch the complete documentation index at: https://docs.arcuserp.com/llms.txt > Use this file to discover all available pages before exploring further. # Marketplace Listings and Mapping > Connect Arcus products and variants to Shopify, Amazon, eBay, and other marketplace listings so imported orders, inventory sync, price sync, and listing performance reports point at the correct canonical item. Marketplace mapping is a control point. A listing can exist on a channel, but Arcus should not push inventory or pricing until the external listing is mapped to the correct product or variant. ## Review Listings On A Product Open a product and select **Listings**. The tab groups marketplace listings by channel and shows whether each connector is available. When a connector is connected, operators can add a listing mapping. When it is not connected, Arcus sends the operator back to Integrations first. Product Listings tab with Shopify connected, one example listing row, Add Listing action, and Amazon and eBay connect actions * **Connected**: Arcus has an active connector for that channel and can add listing mappings. * **Not connected**: connect the marketplace in Integrations before adding a listing for that channel. * **External SKU**: the channel SKU, which may differ from the Arcus SKU. * **Sync inventory**: allows Arcus stock changes to update that listing when the connector supports it. * **Sync price**: allows Arcus pricing to update that listing when the connector supports it. **Map the exact sellable item** If the marketplace sells a variant, map the listing to the exact variant. Mapping a variant listing to the parent can make orders, inventory, and reporting look correct at a glance but wrong in the warehouse. ## Choose The Right Mapping Target The correct target is the Arcus item that should receive the imported order line and supply the inventory or price value sent back to the channel. * **Single physical SKU**: map the external listing to the physical product. * **Marketplace variant**: map the external variant to the matching Arcus child variant, not the variant parent. * **Kit listing**: map to the kit or variant kit that customers buy, then let fulfillment consume the components. * **Service listing**: map only when the channel line should become a service product in Arcus. * **External bundle managed outside Arcus**: do not approve the mapping until support confirms whether Arcus or the channel owns inventory for that bundle. **One channel SKU can still need human review** Exact SKU text is strong evidence, but it is not a guarantee. Review title, option values, channel, and product type before approving sync on a row. ## Add A Listing Mapping 1. Open the product or variant parent record. 2. Go to **Listings**. 3. Find the connected marketplace channel. 4. Click **Add Listing**. 5. For Shopify, review the variant search results when Arcus finds candidates by SKU. 6. If the search does not find a candidate, enter the external listing or variant ID manually. 7. Confirm the external SKU and external title when available. 8. Choose whether inventory and price sync should be enabled. 9. Click **Add Listing**. Add Shopify Listing dialog with Shopify variant search, External ID, External SKU, External Title, Sync inventory, and Sync price controls **Leave price sync off until pricing is verified** Inventory sync and price sync are separate choices. If channel prices have not been audited against Arcus pricing rules, map the listing first and enable price sync after the merchandising or finance team confirms the result. For Shopify, Arcus searches by the Arcus SKU when the product has one. One clear candidate can fill the external fields for review; multiple candidates require the operator to choose the correct external variant. If there are too many close matches, refine the SKU or use the manual External ID fallback instead of guessing. Inventory sync starts on by default in the dialog, while price sync should stay off until the channel price has been audited. ## Use The Mapping Inbox The Marketplace Mapping Inbox is for listings that arrived from a channel and still need human review. It keeps unmapped listings, suggested Arcus matches, drift rows, and bulk mapping work in one place. Marketplace Mapping Inbox Unmapped Listings tab with an example Shopify listing, external SKU, suggested matches, match tiers, similarity scores, and Approve mapping buttons * **Unmapped Listings**: listings that need a canonical product or variant before Arcus can treat them as mapped. * **Suggested matches**: candidate products based on SKU and title similarity. * **Approve mapping**: binds the listing to the selected Arcus item and activates the listing mapping. * **Reject**: removes the listing from the inbox when it should not be mapped. Approving a row makes the listing active for that Arcus product or variant. After approval, review whether inventory sync and price sync should stay on. A listing can be mapped for order identity while price sync remains off until the pricing team finishes its audit. **Approve only when the product identity is clear** Similar SKU or title text is a clue, not proof. Review the product, variant, channel, and external SKU before approving a mapping that can affect sync and reporting. ## Resolve Inventory Drift Drift appears when Arcus and the marketplace disagree about listing quantity. Use the drift tab to review the Arcus quantity, channel quantity, difference, and available resolution actions. Marketplace Mapping Inbox Inventory Drift tab with Arcus quantity, Shopify quantity, delta, Push Arcus, Pull Shopify, and Ignore actions * **Push Arcus**: mark the row resolved after using Arcus as the quantity source. * **Pull Shopify**: mark the row resolved after using the marketplace quantity as the source. * **Ignore**: close the row when the mismatch is intentional or not worth action. Use **Push Arcus** when Arcus inventory is the trusted source and the marketplace should be corrected. Use **Pull Shopify** only when the channel quantity is known to be right and Arcus must be updated or reconciled. Use **Ignore** for intentional channel differences, temporary maintenance, or rows that will be corrected by a separate process. **Find the reason before resolving repeated drift** Repeated drift can come from manual channel edits, delayed marketplace sync, unmapped variants, order imports, cancelled orders, or inventory corrections. Fix the source, not just the visible row. ## Use Bulk Map For Shopify Bulk Map pulls the connected Shopify catalog and compares Shopify variant SKUs to unmapped Arcus products. Use it when a large catalog needs first-pass mapping or cleanup after a connector is connected. Marketplace Mapping Inbox Bulk Map tab with Start Shopify Bulk Pull action, match count, exact and partial score rows, selection controls, and Confirm Selected button 1. Open **Products** and go to **Marketplace Mapping Inbox**. 2. Select **Bulk Map**. 3. Click **Start Shopify Bulk Pull**. 4. Wait for the catalog pull to finish. 5. Review exact and partial SKU matches. Exact SKU matches are strong candidates; partial matches still need human review. 6. Use selection controls only for rows that are correct. 7. Click **Confirm Selected**. 8. Spot check the Product Listings tab after confirmation. Bulk Map polls the Shopify catalog pull while it runs and then shows matched and unmatched rows. Unmatched products are not a failure by themselves; they are the cleanup list for missing SKUs, discontinued channel variants, or products that should stay unmapped. **Do not confirm a weak bulk match** Bulk Map is a review accelerator. It does not replace product identity review, especially for variant families, reused channel SKUs, old discontinued listings, or products with similar names. ## How Listing Mapping Affects Other Workflows * **Imported orders**: mapped listings help Arcus attach imported marketplace lines to the correct product or variant. * **Inventory sync**: mapped listings are the targets for stock pushes when sync is enabled. * **Price sync**: mapped listings are the targets for price pushes when price sync is enabled. * **Fulfillment sync**: connector fulfillment updates depend on the imported order and listing relationship. * **Reporting**: Listings Performance and channel reports are more useful when listing rows point at canonical products. * **Support**: product, order, and channel troubleshooting is faster when the external SKU and Arcus SKU are connected. ## Common Blocks * **Add Listing is missing**: connect that marketplace under Integrations first. * **Shopify search finds no candidate**: confirm the Arcus SKU matches the Shopify variant SKU, or use manual External ID entry. * **Multiple candidates appear**: compare SKU, title, variant option, channel, and product identity before selecting one. * **Inventory updates the wrong listing**: verify the listing is mapped to the exact product or variant being sold. * **Drift keeps coming back**: review manual marketplace edits, connector health, order imports, and inventory corrections. * **Bulk Map shows too many partial matches**: clean up Arcus SKUs and Shopify variant SKUs before confirming a large batch. * **Unmatched rows remain after Bulk Map**: review whether the channel SKU is missing, discontinued, intentionally unmapped, or represented by a different Arcus variant. ## Related Articles Create physical products, services, and product records. Generate variants, manage child SKUs, use the variant editor, and set variant kit behavior. Connect Shopify, Amazon, and eBay, review sync settings, mapping, webhooks, logs, and marketplace blocks. Analyze marketplace listings by channel, units sold, revenue, status, and zero-sales candidates. Configure order-source defaults, connector-owned channels, customer portal access, shared links, and portal branding. Monitor stock health, location balances, low-stock alerts, and inventory value warnings.