Integrations

What Specify connects to

Three lists. What works today. What your developer can build on it. And what is not built yet.

You will find no wall of logos here. We only show a link that exists.

Where Specify sits

Orders come in on the left. Your own systems sit on the right. Each line says how it works today.

  • Available today
  • Through Specify
  • Planned
  • Not yet

Where orders come from

  • Your store, on your own domain Available today
  • AI assistants, through the agent API Available today
  • Your old shop, brought across once by our team Available today

Specify

  • Products and their options
  • What you can make, and what you will not
  • Cart, checkout and orders
  • Requests you could not meet yet

Your systems

  • Card payments, in your own Stripe account Available today
  • Email to your customers Available today
  • Your ERP, books, stock or workshop, through the store API Through Specify
  • Your CRM, through the store API Through Specify
  • Webhooks, so your systems hear of a new order Planned
  • Ready links to an ERP, CRM, books or a carrier Not yet

Available today

These work now. Each one says who switches it on.

  • Card payments

    Available today

    Shoppers pay on a Stripe payment page, in your own Stripe account. Refunds are real too.

    Who switches it on

    You. Connect your account on the Payments screen.

  • Products from your old shop

    Available today

    We bring your products across once. From a Shopify or WooCommerce export, or from your own shop's pages. It is not a sync.

    Who switches it on

    Our team runs it. You check it and say yes.

  • The agent API

    Available today

    AI assistants can ask your store what it can make, and at what price. They can send a request or place an order. The buyer pays on your own payment page.

    Who switches it on

    Nothing to switch on. Every store with a published Capability Map answers it.

  • The store API

    Available today

    Your own systems can read orders and requests. They can move an order on and set stock counts.

    Who switches it on

    You. Make a key in the admin, limited to the jobs it needs.

  • Email to your customers

    Available today

    Order emails work from the first day. Replies go to your own contact address.

    Who switches it on

    Nothing to switch on. Our team sets up sending from your own domain.

  • Your own domain

    Available today

    Your store runs on your own web address.

    Who switches it on

    You, once you have chosen a plan. You add one DNS record.

  • Company sign-in

    Available today

    Your staff log in to the admin with their work account. It uses the OpenID Connect standard.

    Who switches it on

    You, as the owner or an admin.

  • Search engines

    Available today

    Each store has its own sitemap. Its products carry data that search engines can read.

    Who switches it on

    Nothing to switch on.

Integration through Specify

No ready link to your system? Your developer, or a partner, can build one on the store API.

The store API is described in one OpenAPI document. The version is in the path. Within a version, changes only add.

A key can be limited to just the jobs it needs. You can revoke it at any time.

https://api-dev.specify.digital/openapi/store.json

Open the store API document

  • Orders into your ERP or books

    Through Specify
    What the store API gives
    Every order that changed since a given time, oldest first. Then each order in full.
    What is missing
    A ready link to a named system.

  • Order status back from your workshop

    Through Specify
    What the store API gives
    Accept an order, start making it, ship it and close it. The same steps as in the admin.
    What is missing
    Tracking is a line of text. There is no carrier link.

  • Stock counts from your ERP or warehouse

    Through Specify
    What the store API gives
    Set the count for each product and variant, with a reason.
    What is missing
    A way to send many products in one call.

  • Requests into your CRM

    Through Specify
    What the store API gives
    Read the requests your store could not meet yet.
    What is missing
    Your CRM has to ask. Nothing is sent to it yet.

  • Job sheets for the workshop

    Through Specify
    What the store API gives
    The job sheet for each order line, as data.
    What is missing
    Nothing sends it on by itself.

  • Prices and products from your ERP or PIM

    Not yet
    What the store API gives
    Nothing yet. Products and prices are edited in the admin.
    What is missing
    A safe way for a machine to write them.

Planned, or not yet available

None of these works today. We say which one is planned.

  • Webhooks

    Planned

    Your systems would hear of a new order or request as it happens. Today they have to ask.

  • A ready link to an ERP, PIM or OMS

    Not yet

    There is none today. Your developer can build one on the store API.

  • A ready link to your accounting system

    Not yet

    Orders do not reach your books by themselves yet.

  • A ready link to a CRM

    Not yet

    Requests wait in your admin. Your CRM has to fetch them.

  • Shipping labels and tracking from a carrier

    Not yet

    You type the tracking number in when you ship.

  • Apps for no-code tools

    Not yet

    There is no app for them yet. A tool that can send a web request can call the store API.

  • A live sync with another shop

    Not yet

    An import happens once. Your old shop is left as it is.

  • An assistant paying for its buyer

    Not yet

    An assistant can place the order. The buyer still pays on your payment page.

When you need a link that is not built

We can build it with you as consulting work.

It is scoped and priced before it starts.

See how consulting works

See it from the inside

Create a store. Its keys are in the admin, under API keys.

Create your store Read about the agent API

To sign up, we ask for your work email and your company name.