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": "unknown-plugin:dropshipping-xml-for-woocommerce/dropshipping-xml-for-woocommerce",7 "plugin":
9 "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.",
19 "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 Wix.\" 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.",
20 "conclusion": "SPI / partner-gated surface, not a general write API reachable by a normal site migration. No import path exists today for this capability."
21 }
22 ],
23 "decidedBy": "user",
24 "decidedOn": "2026-08-12",
25 "decisionContext": "the mapping review gate, resolving a previously open question (left as a genuine open question in mapping-gaps.json rather than silently resolved).",
26 "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."
32 "reason": "Dropshipping supplier-linkage: same finding as dropshipping-xml-for-woocommerce -- no general-merchant-facing Wix write API for supplier catalog/fulfillment linkage.",
41 "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.",
42 "conclusion": "SPI / partner-gated surface, not a general write API reachable by a normal site migration. No import path exists today for this capability."
43 }
44 ],
45 "decidedBy": "user",
46 "decidedOn": "2026-08-12",
47 "decisionContext": "the mapping review gate, resolving a previously open question (left as a genuine open question in mapping-gaps.json rather than silently resolved).",
48 "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."
54 "reason": "Dropshipping supplier-linkage: same finding as dropshipping-xml-for-woocommerce -- no general-merchant-facing Wix write API for supplier catalog/fulfillment linkage.",
63 "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.",
64 "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."
65 }
66 ],
67 "decidedBy": "user",
68 "decidedOn": "2026-08-12",
69 "decisionContext": "the mapping review gate, resolving a previously open question (left as a genuine open question in mapping-gaps.json rather than silently resolved).",
70 "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)."
71 },
72 {
73 "capability": "commerce.abandoned-carts",
74 "reason": "Historical abandoned carts cannot be imported into Wix. The eCommerce AbandonedCheckout entity has NO create, import or upsert method at any level — the whole public AbandonedCheckoutService is Get / Delete / BulkDelete / Query / Search / RedirectToCheckout — and the entity is only ever derived by the platform from a live shopper session that went incomplete. The documented workaround (recreate the antecedent cart and let the pipeline detect it) was piloted live and does not work: carts created live, including one carrying a genuine platform-assigned visitorId plus a Wix-resolved contactId, produced ZERO AbandonedCheckout records, however long they sat. Even had it worked, Cart.createdDate is readOnly, so every backfilled cart is stamped with the import date rather than the real abandonment date: a year of history would read as abandoned today and would trigger recovery mail about carts people left months ago. Do NOT attempt this path. The PEOPLE behind abandoned carts are a separate matter and remain migratable as crm/contact (email only, never a subscription status — an abandoned cart is not consent).",
75 "searched": "2026-09-07/08. (1) SearchWixRESTDocumentation 'create abandoned checkouts / import historical abandoned cart records' -> only Get/Query/Search/Delete/BulkDelete plus created/updated/recovered/deleted webhooks; the API introduction states the platform creates the entity itself when a customer starts a checkout or a member abandons a cart. (2) Full method enumeration of the AbandonedCheckout resource via the API spec (resourceId 078d1b42-5b92-4ad4-8160-01247260582e): 6 methods, no create at any level. (3) Cart schema inspection: buyerInfo.visitorId / memberId / userId are all readOnly (platform-assigned from the calling session) and Cart.createdDate is readOnly. buyerInfo.contactId is writable in the schema but REFUSED in practice on the admin path — sent at CreateCart and again at UpdateCart, read back null both times. (4) Live pilot: admin-token carts (no identity) and a visitor-token cart (contactId auto-resolved by Wix from the buyer email) — none classified. The Stores catalog gate passed, so the catalog was never the blocker. (5) The Wix Stores AbandonedCarts CMS collection is a read-only Wix App system collection, not an authorable target.",