Resources · Make integration

ScanOrders Make integrationAutomate ScanOrders with Make.

Can Make react when a fulfilment is picked in ScanOrders? Yes. The ScanOrders Make integration gives you 3 modules: 1 scheduled trigger and 2 actions. This guide links your account, then walks you through a first scenario you can test before it runs on its own.

Try the ScanOrders integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the ScanOrders Make integration do?

The ScanOrders Make integration links your ScanOrders account to Make, a visual tool where you build automations called scenarios: chains of small bricks, the modules, that pass data from one app to the next. For ScanOrders, Make offers one module that watches picked fulfilments and two that act in the app.

Hand picked fulfilments to the rest of your tools. Watch Picked Fulfilments starts a scenario each time Make finds a fulfilment in that state. From there you add a module of another app: a row in a sheet, a message to the team, a record in your CRM. Each fulfilment travels as one bundle, the item Make passes from one module to the next.

Open fulfilments from another app. Create Fulfilment works the other way around. Put a trigger from another app first (a form, a sheet, a shop) and let ScanOrders receive the fulfilment without anyone typing it in.

Reach what the menu does not list. Make an API Call reuses your connection to call any endpoint of the ScanOrders API, which covers the gaps of a short catalog.

Be clear on one limit: Make's own documentation for ScanOrders is thin, because little public information exists about the app. The field names appear in each module once your account is connected, not before. If a scenario stalls, the Make troubleshooting guide covers the usual suspects, and the Make pricing page explains how operations are counted. Hesitating between the two platforms? Read n8n vs Make.

Connect

How do you connect ScanOrders to Make?

  1. 01

    Add a ScanOrders module

    Open a scenario, click the +, search for ScanOrders and pick any of its modules. In the module window, click Create a connection. A connection is your ScanOrders account linked to Make once, then reused by every ScanOrders module.

  2. 02

    Name the connection

    This step is optional, and still useful. Give the connection a name you will recognize later, such as the store or the team it belongs to, so you pick the right account when several scenarios share it.

  3. 03

    Authorize and save

    Make then asks for what ScanOrders requires: either you approve access on a ScanOrders page, or you paste the key the app gives you. Click Save. The module can now read your ScanOrders data and list what it finds.

First scenario

Your first scenario with ScanOrders

GoalWhen a record lands in another app, Make creates the matching fulfilment in ScanOrders.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the + in the middle of the canvas. That empty circle becomes the first module, the one that starts everything.

  2. 02

    Pick the starting app

    Choose the app where the information first appears, for example a form or a spreadsheet, and its watch module. Connect that account the same way you connected ScanOrders.

  3. 03

    Add Create Fulfilment

    Click the + on the right of the first module, search for ScanOrders and choose Create Fulfilment. Select your connection. Make then shows the fields ScanOrders accepts.

  4. 04

    Map the data

    Fill each field by clicking into it and picking values from the first module. Make keeps the link, so every new bundle brings its own values instead of a fixed text.

  5. 05

    Test with Run once

    Click Run once, then trigger a real event in the starting app. Open the bubbles above each module to read the bundles they received and check the new fulfilment in ScanOrders.

  6. 06

    Schedule and switch on

    Click the clock on the first module to set how often it runs (every 15 minutes by default), then turn the scenario on. Each module run on each bundle counts as one operation on your plan.

Triggers

What starts a ScanOrders scenario

1 module starts a scenario when something happens in ScanOrders. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by ScanOrders as soon as it happens.

ScanOrders1Watch Picked Fulfilments

Watch Picked Fulfilments

triggerIn the docs only

Watch Picked Fulfilments hands your scenario every fulfilment that has reached the picked stage, one bundle per fulfilment, so the next steps follow without copying data by hand.

How it fires
it is a scheduled trigger, a type deduced from its name. Make checks ScanOrders on the scenario's schedule (the clock badge), every 15 minutes by default, and 1 minute at the shortest on paid plans.
When to use it
pick it when another tool must hear about each picked fulfilment, such as the shipping team's chat.
Watch out
since Make describes nothing here, click Run once and read a real bundle before you switch the scenario on.
Modules

What the ScanOrders modules do

ScanOrders gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

ScanOrders1

Create Fulfilment

ActionIn the docs only

Create Fulfilment gives you a new fulfilment in ScanOrders built from data another module passes along, so nobody retypes it. It is an action: it works on one bundle at a time.

When to use it
choose it when the information starts outside ScanOrders, in a form, a sheet or a shop, and ScanOrders must receive it.
Watch out
the fields are only visible after you connect, since the Make documentation does not list them.
ScanOrders2

Make an API Call

ActionIn the docs only

With Make an API Call you reach any endpoint of the ScanOrders API while keeping the connection you already set up, which fills whatever the two other modules leave out.

When to use it
reach for it only once Watch Picked Fulfilments and Create Fulfilment clearly cannot do the job.
Watch out
you write the request yourself, so ask ScanOrders for its API documentation before you start.
Need help

Need help automating ScanOrders with Make?

A person reads every message.

FAQ

Questions about the ScanOrders Make integration

01Is the ScanOrders Make integration free?
Yes, ScanOrders is a standard app in Make, so it works on the Free plan. That plan has limits: 2 active scenarios, 15 minutes at least between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module run on one bundle. What ScanOrders itself costs is a separate question for ScanOrders.
02What do you need to connect ScanOrders to Make?
A ScanOrders account and a Make account. The Make documentation lists no special prerequisite and no official connection steps for ScanOrders, so the generic flow applies: add a ScanOrders module, click Create a connection, optionally name it, then approve access on the ScanOrders page or paste the key the app provides, and save. The connection is created once and every ScanOrders module in your scenarios reuses it. If the window asks for something you do not have, look in your ScanOrders account settings first.
03Does the ScanOrders trigger in Make fire in real time?
No. Watch Picked Fulfilments is a scheduled trigger (Make lists it without a description, so the type is deduced from its name): Make checks ScanOrders on the scenario's schedule rather than being told by the app. A new scenario checks every 15 minutes by default. On the Free plan 15 minutes is also the shortest interval, and paid plans go down to 1 minute. ScanOrders offers no instant trigger in Make, so if you need a faster reaction, shorten the schedule on a paid plan.
04What if the ScanOrders module you need is missing in Make?
Use Make an API Call. It relies on the connection you already have and can call any endpoint of the ScanOrders API, so it covers what Watch Picked Fulfilments and Create Fulfilment do not. The catch is that you build the request yourself from the API documentation ScanOrders gives you. Keep in mind that the Make documentation for ScanOrders is limited because little public information exists about the app, so test each call with Run once and read the bundle it returns before switching the scenario on.
05Should you use Make or n8n for ScanOrders?
It depends on your criteria, not on a ranking. In Make, ScanOrders comes with 3 modules: 1 scheduled trigger, 2 actions including Make an API Call, and it runs on the Free plan. Many apps also have an n8n node, but this guide does not document whether ScanOrders is one of them, so check the n8n side before deciding. Compare what each tool offers for your exact steps, how you prefer to build, and who will maintain the scenario. Neither tool is presented here as faster or cheaper for ScanOrders.
Same platform

Other docs you might need on this stack.

Browse all integrations