> For the complete documentation index, see [llms.txt](https://docs.foodcore.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.foodcore.io/shop-integration-core/integrations.md).

# Integrations overview

{% hint style="info" %}
📦 Available on the **Core** plan.
{% endhint %}

Connecting a shop lets FoodCore pick up orders automatically instead of you re-typing them. There are two separate things a shop integration can do, and they're set up in this order:

1. **Orders coming in** (needed) — the shop tells FoodCore about new orders as they're placed.
2. **Fulfilment going out** (optional) — FoodCore tells the shop when an order is ready or delivered.

You can stop after step 1. Plenty of businesses only ever want orders flowing in.

## The ordering constraint

The setup has to happen in a specific sequence, and it trips people up if they don't know why:

The webhook address FoodCore gives you contains the integration's own ID. That means **the shop can't be pointed at FoodCore until the shop record exists here first** — there's no address to give it yet. And the signing secret that proves a webhook really came from your shop only exists once the shop-side webhook itself has been created.

So the order is always:

**Create the shop here → copy the webhook URL → create the webhook in the shop → paste the secret back here.**

Skipping ahead — creating the shop-side webhook before the FoodCore record exists — just means you have nothing to point it at yet.

## "Finish setup" vs "Connected"

A shop card in FoodCore shows one of two states:

* **Connected** — a signing secret is saved, so FoodCore can verify orders really came from your shop.
* **Finish setup** — no secret saved yet.

"Finish setup" doesn't mean the connection is broken. It usually means the shop *can* already reach FoodCore — every delivery attempt is arriving — but FoodCore is turning each one away with a 401 because it can't verify who sent it. That's correct behaviour, not a fault, and it's invisible from the shop owner's side of things: their webhook log will show delivery attempts, just all rejected. The fix is simply to finish pasting the secret in.

## Where products come from

FoodCore doesn't need a full product catalogue from your shop to import orders. Products are **learned from the orders that arrive** — no Shopify custom app or Admin API token is required just to bring orders in.

The first time an order references a product FoodCore hasn't seen before, it's recorded as unmapped. Unmapped products show up in [Business Insights](https://docs.foodcore.io/business-insights-core/business-insights.md) with a pointer through to the mapping screen, so you can link them to the right ingredient or recipe when you get a moment — it doesn't block the order from coming in.

## What's next

* [Shopify setup](https://docs.foodcore.io/shop-integration-core/shopify.md)
* [WooCommerce setup](https://docs.foodcore.io/shop-integration-core/woocommerce.md)
* [Stripe payment links](https://docs.foodcore.io/payments-core/payment-links.md)
* [Business Insights overview](https://docs.foodcore.io/business-insights-core/business-insights.md)
