1{2 "schemaVersion": 1,3 "description": "The Requires development register: capabilities a NAMED HUMAN has determined Wix has no surface for. This is the only place that verdict may live, and the only source of the requires-development status — automation is limited to migration-planned, no-need-to-migrate, or pending.\n\nWhy the restriction: an agent concluded twice that Wix had no target (gift cards, events) and was wrong both times, because Wix splits capabilities across doc trees and a service plugin reads like an absent write API. A wrong 'impossible' is the most expensive error in this system: it tells a customer to abandon data that could have moved.\n\nEvery entry needs `decidedBy` and `decidedOn` alongside the recorded search. Entries are reviewable and reversible: if a target later appears, validation rejects the entry.",4 "capabilities": [5 {6 "capability": "commerce.product-bundles",7 "reason":
"Fixed product bundles (one purchasable product composed of specific child products with quantities at a set price — WPC Product Bundles' woosb_ids, and the official WooCommerce Product Bundles / Composite Products extensions alike) have no native Wix Stores target: Catalog V3 productType is PHYSICAL | DIGITAL only, with no composed-product entity or child-product references, and order history's parent/child line-item linkage (_woosb_ids / _woosb_parent_id) has no eCom order field to receive it. Interim migration path: the bundle product migrates as a plain stores/product with its derived price frozen at migration-time value, and the composition lands in a CMS collection keyed by the product crosswalk — the same shape Wix's own Velo 'Bundle Products' package uses."
,
8 "searched": "bundle, composite product, product kit, product set, child products — dev.wix.com and support.wix.com (2026-08-16, WebSearch/WebFetch): Catalog V3 product-object.md (productType PHYSICAL|DIGITAL only); dev.wix.com/docs/velo/articles/velo-package-readmes/wix-stores-bundle-products (Velo site-code pattern: plain product + CMS Bundles collection, not a write API); support.wix.com/en/article/wix-stores-selling-mix-and-match-product-bundles — evaluated 2026-08-16 at Spec Owner's request: mix-and-match is a category + automatic-discount pattern for customer-assembled combos (no fixed-bundle SKU, no composed-product entity, no API) and does NOT receive fixed bundles.",
9 "decidedBy": "Spec Owner",
10 "decidedOn": "2026-08-16",
11 "note": "Tracked separately as a Wix API feature request (Stores/Catalog: bundle/composite product type writable at creation). Per the owner-ask policy, a gap with a working workaround (CMS composition) gets no standalone owner task. Reversible: if Catalog V3 gains a bundle primitive, validation rejects this entry once a target entity claims the capability."
17 "reason": "Dropshipping supplier-linkage: no general-merchant-facing Wix write API represents linking a store's products to an external dropshipping supplier's catalog/fulfillment feed.",
27 "found": "The business-solutions tree does have a Marketplace Suppliers API (suppliers-hub) whose Supplier object carries a DROPSHIPPING/WHOLESALE type -- but per its own docs, quoted verbatim: \"This API is available only to approved Wix business partners and requires a signed business agreement with Wix. To apply for partnership, contact jills@wix.com.\" Its `Supplier` models the marketplace-provider relationship (an entity that supplies a Wix *marketplace provider*, who then resells to end users), not a per-product external-supplier link an ordinary merchant's own store can create on its own products. The other hits (\"Extensions and APIs for Dropshipping Apps\", Catalog V3) are for *building* a dropshipping-supplier app that provides products TO other Wix stores (an SPI direction), or for generic inventory/stock management -- neither is a write path for importing an existing store's own supplier-linkage configuration.",
28 "conclusion": "SPI / partner-gated surface, not a general write API reachable by a normal site migration. No import path exists today for this capability."
29 }
30 ],
31 "decidedBy": "user",
32 "decidedOn": "2026-08-12",
33 "decisionContext": "the mapping review gate, resolving a previously open question (left as a genuine open question in mapping-gaps.json rather than silently resolved).",
34 "searched": "dropshipping supplier catalog sync, supplier fulfillment linkage, dropship product import API — searched against dev.wix.com business-solutions tree (WebSearch/WebFetch, 2026-08-12). Found the Marketplace Suppliers API (suppliers-hub), but it is restricted to approved Wix business partners with a signed business agreement and models the marketplace-provider relationship, not a per-product external-supplier link on an existing store. No general write API found."
40 "reason": "Dropshipping supplier-linkage: same finding as dropshipping-xml-for-woocommerce -- no general-merchant-facing Wix write API for supplier catalog/fulfillment linkage.",
49 "found": "Same Marketplace Suppliers API finding as dropshipping-xml-for-woocommerce: partner-gated (signed business agreement required), and its Supplier object models the marketplace-provider relationship, not a per-product external-supplier link on an existing store.",
50 "conclusion": "SPI / partner-gated surface, not a general write API reachable by a normal site migration. No import path exists today for this capability."
51 }
52 ],
53 "decidedBy": "user",
54 "decidedOn": "2026-08-12",
55 "decisionContext": "the mapping review gate, resolving a previously open question (left as a genuine open question in mapping-gaps.json rather than silently resolved).",
56 "searched": "dropshipping supplier catalog sync, supplier fulfillment linkage, dropship product import API — searched against dev.wix.com business-solutions tree (WebSearch/WebFetch, 2026-08-12). Same Marketplace Suppliers API finding as dropshipping-xml-for-woocommerce: partner-gated, not a general write surface."
62 "reason": "Dropshipping supplier-linkage: same finding as dropshipping-xml-for-woocommerce -- no general-merchant-facing Wix write API for supplier catalog/fulfillment linkage.",
71 "found": "Same Marketplace Suppliers API finding as dropshipping-xml-for-woocommerce: partner-gated (signed business agreement required), and its Supplier object models the marketplace-provider relationship, not a per-product external-supplier link on an existing store. Note: Syncee is also independently available as a Wix App Market app for merchants, which is a separate reconfigure-in-wix path a merchant could adopt fresh in Wix -- but that is not a migration of this plugin's existing WooCommerce-side linkage/data, which is what this capability tracks.",
72 "conclusion": "SPI / partner-gated surface, not a general write API reachable by a normal site migration. No import path exists today for this capability's existing source-side configuration."
73 }
74 ],
75 "decidedBy": "user",
76 "decidedOn": "2026-08-12",
77 "decisionContext": "the mapping review gate, resolving a previously open question (left as a genuine open question in mapping-gaps.json rather than silently resolved).",
78 "searched": "dropshipping supplier catalog sync, supplier fulfillment linkage, dropship product import API — searched against dev.wix.com business-solutions tree (WebSearch/WebFetch, 2026-08-12). Same Marketplace Suppliers API finding: partner-gated, not a general write surface for migrating this plugin's existing source-side linkage/data (Syncee's own Wix App Market app is a separate reconfigure-in-wix path, not a migration of this data)."