What it does
The engine repository contains adapter code for ten e-commerce platforms: Shopify, WooCommerce, BigCommerce, Magento, Medusa, Saleor, commercetools, Vendure, PrestaShop and Wix. The server never calls that code, so no catalogue is imported today. The adapters have tests as a library, but no running part of the product can use them, which is why this entry is roadmap.
How it works
Each adapter implements one contract: a full catalogue backfill that pages through the platform API and writes products into an engine, a handler that applies a single platform event (create, update or delete), and a single-product fetch. Products use the e-commerce domain model of the engine. A shared HTTP client and a registry that finds an adapter by name sit beside them.
The server crate lists the connector library as a dependency but contains no call into it. Two routes mention connectors: one lists the adapter names, and one accepts a webhook request for a named adapter, acknowledges it and imports nothing. No setting, route or command starts a backfill or applies a platform event.
The tests build products from sample platform payloads, map product status and prices, and apply events to an engine opened on a temporary directory. They do not call a platform. The paging code that talks to each platform API has no test.
Where you reach it
- Library
kynetra-connectors crate: Connector trait, ConnectorRegistry and ten adapters (library code; the server does not call it)
Limits
- Not reachable. Nothing in the server, the command-line tool or an SDK runs these adapters.
- No adapter has been run against a live platform in the engine repository. The tests use in-memory fixtures.
- The routes the server exposes for connectors acknowledge a request and import nothing. Do not point a platform at them expecting a catalogue to arrive.
- To get product data in today, use the REST layer, the HTTP API or the migration tool.
Evidence
- TestsCovered as a library in the engine repository by more than 80 tests across the ten adapters (field mapping, status mapping, price handling, applying create, update and delete events to an engine). None runs against a live platform, and none covers backfill paging.
Test coverage is listed as present in the engine repository at this edition. This page does not report test results.
KynetraDB is in private preview
This is not available in the preview. Request a preview to discuss the current scope.