Developers

Start with a file. Add feeds and the live cart when you’re ready.

Zyntel is API-first, but you don’t need an integration to start. Upload your catalogue, sales and stock, take recommendations as a daily file, and connect systems one at a time.

Everything you need, nothing you have to build first.

  • Catalogue & sales upload

    CSV or Excel uploads for catalogue, sales, stock and on-order data. Field matching maps your names to ours.

    Example“Style code” is our product code.

  • Data feeds

    Daily or hourly feeds from your ERP, POS and ecommerce platform, with expected arrival times and health checks.

    ExampleStock from your ERP daily at 3 am.

  • Recommendation feed

    Approved decisions sent daily as Excel, CSV or a direct feed, with draft purchase orders and transfers.

    ExampleRecommendations-only mode needs nothing else.

  • Decision API

    Send a basket or a product context and get back the offer to apply, checked against caps, limits and the margin floor.

    ExampleLive cart mode.

  • Event hooks

    Get notified when a recommendation is approved, an offer starts or stops, or a feed is late.

  • Test workspaces

    Build and test against isolated data before you go live.

Four stages. Stop at whichever suits you.

  1. Start

    You sendFile uploads

    You getA daily recommendation file

  2. Connected

    You sendDaily feeds from ERP, POS, ecommerce

    You getRecommendations, draft POs and transfers in your systems

  3. Measured

    You sendOrder data back each day

    You getResults measured against holdout stores

  4. Live cart

    You sendBasket context at checkout

    You getThe offer to apply, checked against every limit

Developer questions

Do we need an integration to start?

No. Upload your catalogue, sales and stock as CSV or Excel, and take recommendations as a daily file. Feeds and the live cart can come later.

How do we know a feed arrived?

Every run reports which feeds arrived, which were late, and which rows were set aside and why. Automatic decisions pause below 95% data health.

How do we test safely?

Build and test against isolated data in a test workspace before you go live.

09Walkthrough on your data

Bring one category. See tomorrow’s worklist.

We load a sample of your catalogue, sales and stock, run the engine on it, and walk you through every recommendation, the reason behind it and what it would have earned.

Go live with as few as 100 SKUs and any length of sales history.

  • Your catalogue and stock, loaded
  • SKU health and risk scores
  • Buy, move and markdown calls
  • Festival effects for your regions
  • Your brand and store rules
  • Live cart or recommendations only
  • What it would have saved
  • A rollout plan by category