⚡ Marketplace — supplier portal

1. In Shopify admin, go to Settings → Apps and sales channels → Develop apps. If you see "Allow custom app development", click it to enable it (owner permission required).
2. Click Create an app, name it (e.g. "X402 Market"), then open Configuration → Admin API integration → Configure.
3. Tick the scopes read_products and read_inventory, then Save.
4. Open the API credentials tab and click Install app. Shopify reveals the Admin API access token (starts with shpat_). Copy it now — Shopify shows it once.
5. Back here: choose connector shopify, put your shop domain in URL / shop domain (e.g. mystore.myshopify.com — not your custom domain), and paste the shpat_ token in Credential. Click Create.
6. Click sync on the new integration row to pull your catalog now. Variants (sizes/colors), images, prices and stock come across automatically, and we re-poll every 15 minutes.

Tip: taking a product down in Shopify sets it out of stock here on the next poll. You can also point a Shopify webhook (products/create, update, delete) at the URL shown after creation for instant updates.

1. In WordPress admin, go to WooCommerce → Settings → Advanced → REST API and click Add key.
2. Description: "X402 Market". User: an admin user. Permissions: Read is enough. Click Generate API key.
3. Copy the Consumer key (ck_…) and Consumer secret (cs_…) — the secret is shown once.
4. Back here: choose connector woocommerce, put your site URL in URL (e.g. https://shop.example.com), and enter the credential as ck_xxx:cs_xxx (key, colon, secret) in Credential. Click Create.
5. Click sync to pull now; polling continues every 15 minutes. Your site must be reachable over HTTPS with pretty permalinks enabled (WooCommerce requires this for its REST API).

Tip: click test before syncing — it shows the first records exactly as they'll be mapped, so you can spot price/stock field problems before anything publishes.

1. Expose one HTTPS GET endpoint from your ERP/inventory system that returns JSON like: {"items":[{"id":"1001","title":"Copper Pipe","sku":"CU-34","price":28.40,"quantity":240,"category":"plumbing","brand":"Acme","keywords":"pipe, copper, plumbing"}]}
2. Back here: choose connector rest and paste that endpoint into URL.
3. If your JSON array lives under a different key than items (e.g. {"data":{"products":[…]}}), put its dot-path in Items path (e.g. data.products).
4. If the endpoint needs auth, put the bearer token / API key in Credential — we send it as Authorization: Bearer <key>.
5. Field names differ per system? The defaults map id, title, description, sku, price, quantity, category, brand, keywords. Anything else can be remapped via the API: POST /api/v1/integrations with config.mapping using dot-paths (e.g. "price":"pricing.retail.usd").
6. Click Create, then test (previews the mapping on live records), then sync. We re-poll your endpoint every 15 minutes, so stock and prices track your ERP.

Tip: a live demo feed exists at /demo/erp-feed.json on this site — point a rest connector at it to see the whole flow end-to-end.

1. Export your inventory to CSV from Excel, Google Sheets, QuickBooks, your POS, etc.
2. Columns are auto-detected by header name. Recognized (case-insensitive): sku / part number, title / name / product name, description, price / unit price, quantity / qty / stock / on hand, category / type, brand / vendor, image url (| separated for several), taxable (yes/no), keywords / search terms (comma separated, up to 3).
3. Easiest path: go to the Products tab, pick your file next to "bulk CSV" and click Import CSV — a CSV integration is created for you automatically.
4. Scripted path: create a csv connector here, then POST the raw file to /api/v1/integrations/{integration_id}/csv with Content-Type: text/csv and your API key.
5. Re-uploading the same file updates existing items (matched by SKU) instead of duplicating them — safe to re-import nightly.

Tip: rows missing a title or price are skipped and reported; nothing partial is ever published.

1. Create a webhook connector here (only a name is needed). The success message shows YOUR unique inbound URL: /webhooks/generic/{integration_id}.
2. Configure your system (ERP, POS, middleware, Zapier/Make) to POST product events to that URL as JSON. Send either one item or {"items":[…]}, using the same fields as the REST connector (id, title, sku, price, quantity, …).
3. Creates and updates are matched by sku/id; send "deleted": true (or quantity 0) to take an item off sale.
4. Using Shopify webhooks instead of polling? Point products/create, products/update, products/delete at /webhooks/shopify/{integration_id} — the native Shopify payload is understood as-is.
5. No polling delay: changes appear in the agent catalog the moment your system fires.

Tip: webhook and a pull connector can run side-by-side — pull keeps you reconciled every 15 minutes, push makes changes instant.

1. Create a daemon connector here. The success message shows your integration_id, api_key and hmac_secret — and you can view them again any time with the creds button in the connector list.
2. Download the connector, unzip it inside your app's root folder, then run npm install && npm start.
3. A portal opens at http://localhost:7402. It auto-discovers your database from .env, wp-config.php, config/database.yml or local SQLite files — or paste a connection URL.
4. It scans your schema on a read-only connection and proposes a field mapping (AI-assisted; only schema goes to the mapper unless you opt in to 3 redacted sample rows). You review 5 preview products and can edit every field before approving. Any column that isn't a standard field becomes a dynamic attribute — every product carries all of its fields, whatever they are.
5. On approval it pushes your catalog and holds ONE outbound connection. When an agent buys, the sale is signed, pushed down instantly, and written into your database — a guarded stock decrement, plus (optional) a native order row so the sale appears in your own admin and reports. Offline? Events queue and drain the moment it reconnects. Nothing ever polls.
6. Local stock changes flow back up automatically via your database's own change events (Postgres trigger, SQLite file watch) or the portal's Sync button.

The only writes it can ever perform are the two statements generated from the mapping YOU approved, idempotent per order, all logged to a local audit file.