Seekmodo developer docs
Reference for the REST shim, MCP JSON-RPC surface, and storefront connectors. Authenticate with HMAC; replay window is 5 minutes.
Change platforms without a second Seekmodo bill
Your Seekmodo tenant is the paid account: search history, learning-to-rank, synonyms, pins, fitment, and billing all live there. A connector is only how one storefront talks to that tenant.
When you re-platform (for example Zen Cart → BigCommerce), keep the same production tenant. Install the new connector and pair it to the existing tenant at seekmodo.com/connect. Do not create a second paid tenant for the new store.
What not to do
- Do not sign up for a new Seekmodo plan just because the commerce platform changed.
- Do not pair a sandbox / staging storefront to your production tenant. Use a separate demo or staging tenant (or leave sandbox on a complimentary prospect). Shared indexes mix product URLs across environments.
- Do not leave the old and new production connectors both indexing into the same tenant for a long dual-live period without a product ID migration (see below).
Self-serve today
The guided path is Settings → Change platform in admin.seekmodo.com. It walks Connect → Index → Match → Review → Apply → Retire on your current tenant.
- Finish catalog on the new platform — products, categories, and images must exist in the destination store (your platform migration or import tools, not Seekmodo).
- Install the Seekmodo connector for the new platform. Examples: BigCommerce install, Shopify install, Magento install.
- Pair to your existing tenant — after OAuth (or Connect in the CMS admin), sign in at seekmodo.com/connect (deep-link
?tenant=from the wizard) and select the same production tenant you already pay for. Confirm pairing. - Wait for the first catalog index — the wizard polls until documents appear (or check admin overview).
- Match & apply product IDs — in the same wizard, so learning and merchandising stay warm (see below).
- Smoke-test search — typeahead, Enter on search, and (if you use them) vehicle / recommendations surfaces.
- Retire the old connector — uninstall or disconnect Seekmodo on the old platform when that storefront is no longer public, so it stops writing to the tenant.
Billing stays on the original tenant. No plan transfer ticket is required when you re-pair correctly.
Product IDs change — why it matters
Commerce platforms assign their own product primary keys. After a re-platform, the same SKU usually has a new ID. Seekmodo learning, click history, and some merchandising rules are keyed by those IDs. Pairing alone reindexes the new catalog; it does not rewrite historical IDs.
Without a mapping step, search still works from the new index, but relevance learning and product-keyed merchandising effectively cold start (often 30–90 days to catch up).
ID migration in admin (keeps your learning)
After the new connector is paired and indexed, open Settings → Change platform in admin.seekmodo.com. The wizard matches old → new product IDs (SKU / MPN / UPC / name), lets you review ambiguous rows, dry-runs, then rewrites clicks and merchandising on the same tenant — no Admin Key and no support ticket for the happy path.
- Complete Connect + index steps in the wizard (or pair at /connect?tenant=… first).
- Run Match. Prefer auto-built catalogs from your Seekmodo index; upload a source JSON only if legacy IDs are missing.
- Review low-confidence rows, dry-run, then apply before or as you flip public traffic to the new storefront.
- Uninstall the old connector. Rollback stays available for about 24 hours after apply.
Complex fleet cutovers (multi-tenant force / audit) still go through Numinix ops. Everyday re-platforming uses the in-app wizard only.
Cutover checklist
- New storefront catalog complete and images present
- Seekmodo installed and paired to the existing production tenant (not a new signup)
- First index finished; smoke tests green
- ID migration applied if you care about LTR / pins / fitment overrides keyed by product id
- DNS / launch of the new storefront
- Old platform Seekmodo connector disconnected
Sandbox and demos
Keep sandboxes on a separate complimentary or staging tenant. Pair production only to the paid production tenant. That matches how Seekmodo treats other multi-environment merchants.
Support
- Contact · support@seekmodo.com
- Platform installs: Connectors hub
- Status: status.seekmodo.com