Resources · Make integration

PHP Point of Sale Make integrationAutomate PHP Point of Sale with Make.

What if your register data could update the rest of your tools on its own? The PHP Point of Sale Make integration gives you 25 modules: 4 triggers that watch sales, customers, suppliers and receivings, plus actions and searches. This guide walks store owners and ops leads from connection to a first working scenario.

Try the PHP Point of Sale integration on MakeSee the 25 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the PHP Point of Sale Make integration do for you?

The PHP Point of Sale Make integration links your store account to Make, a no-code tool where you build a scenario, meaning an automation made of modules. Each module is one brick: a trigger that starts the flow, an action that writes something, or a search that finds records. You pick them from a list, no code involved.

Books that follow the stockroom. Watch Receivings spots each receiving you record, and Create an Expense logs a matching expense, so the back office stops retyping delivery paperwork.

A customer list that stays clean. Watch Customers reports every new customer profile. Pair it with a module from your email or CRM tool, or use Search Customers before Create a Customer so a web signup does not produce a duplicate at the register.

Staff records kept in one place. Create an Employee, Update an Employee and Delete an Employee let an HR form or spreadsheet drive the staff list instead of manual edits in the store settings.

Some limits are worth knowing. The official documentation lists modules for customers, suppliers, employees and expenses, and only watch modules for sales and receivings; anything else goes through Make an API Call. The doc page itself warns that it is AI-generated from vendor material, so check important details with PHP Point of Sale. If you are weighing tools, read n8n vs Make, and for plan limits see Make pricing. Teams that want help building can talk to our Make agency.

Connect

How do you connect PHP Point of Sale to Make?

  1. 01

    Copy an API key from your store

    In PHP Point of Sale, open Store Config, scroll to the bottom of the page and click Add API Key. Copy the key shown on screen. You need an active PHP Point of Sale account for this.

  2. 02

    Open the connection window in Make

    Add any PHP Point of Sale module to your scenario and click Create a connection. A connection is your store account linked to Make once, then reused by every module of the app. The Connection name field is optional.

  3. 03

    Paste the key and save

    Enter the credentials you copied from PHP Point of Sale, or follow the on-screen instructions, then save. Make now reads your store data, so the module fields can offer lists instead of blank boxes.

First scenario

Build your first scenario with PHP Point of Sale

GoalWhen a receiving is recorded in PHP Point of Sale, Make logs a matching expense in the same store.

  1. 01

    Start a blank scenario

    Go to the Scenarios page, create a new scenario and click the big + to place the first module on the canvas.

  2. 02

    Pick Watch Receivings

    Search for PHP Point of Sale, choose Watch Receivings and select your connection, or click Create a connection if this is your first module of the app.

  3. 03

    Add Create an Expense

    Click the + on the right of the trigger, pick Create an Expense and map the receiving data you want into its fields. Make lists what it can read once the connection exists.

  4. 04

    Test with Run once

    Click Run once, record a receiving in your store, and open each module to read the bundle it received. A bundle is one item passed along, here one receiving.

  5. 05

    Schedule it and switch it on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, which is also the shortest interval on the Free plan. Then turn the scenario on.

Triggers

Triggers: what starts a PHP Point of Sale scenario

4 modules start a scenario when something happens in PHP Point of Sale. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by PHP Point of Sale as soon as it happens.

PHP Point of Sale1Watch Customers

Watch Customers

triggerIn the docs only

Every customer added to PHP Point of Sale can start a scenario with this trigger, so a new profile reaches your other tools without anyone copying it by hand. Each customer arrives as one bundle you can map into the next module.

How it fires
scheduled. Make checks the app on the scenario's schedule, then processes the customers it finds.
When to use it
a shopper signs up at the counter and you want the contact in your mailing tool or CRM too.
Watch out
each customer found costs operations downstream, so filter early if you only need some of them.
PHP Point of Sale2Watch Receivings

Watch Receivings

triggerIn the docs only

Stock deliveries you record as receivings become the starting point of your automation here. Make picks up each new receiving and hands it to the modules that follow, ready to map into an expense, a message or a sheet.

How it fires
scheduled. Make checks the app on the scenario's schedule rather than being alerted the moment it happens.
When to use it
the back office should see each delivery in its own records without a separate entry.
Watch out
an entry made between two checks waits for the next run, so plan around that delay.
PHP Point of Sale3Watch Sales

Watch Sales

triggerIn the docs only

Your completed sales can feed reports, spreadsheets or team alerts once this trigger sits at the head of a scenario. It returns the new sales it finds, one bundle per sale, for the next module to use.

How it fires
scheduled. Make checks the app on the scenario's schedule. Sales therefore arrive in batches rather than one by one as each ticket rings up at the counter.
When to use it
a manager wants sales copied to a shared sheet or a chat channel after the register closes a ticket.
Watch out
a busy store yields many bundles per check, and every module after the trigger counts one operation per bundle.
PHP Point of Sale4Watch Suppliers

Watch Suppliers

triggerIn the docs only

New vendors added to PHP Point of Sale get picked up by this trigger, which lets purchasing and accounting share one supplier list. Each new supplier travels to the next module as a single bundle.

How it fires
scheduled. Make checks the app on the scenario's schedule and passes along what was added since the previous check.
When to use it
your accountant keeps a vendor register elsewhere and should hear about each new supplier.
Watch out
judging by its name, it looks for new suppliers; to follow later edits, plan a search step rather than count on this trigger.
Modules

Modules: what PHP Point of Sale can do in Make

PHP Point of Sale gives you 21 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

PHP Point of Sale1

Create a Customer

ActionIn the docs only

A new shopper profile lands in your store directly from another app, so online signups and event lists join the register without retyping.

When to use it
a web form or booking tool collects a new client and the counter should recognize them on the first visit.
Watch out
run Search Customers first, otherwise a returning shopper gets a second profile.
PHP Point of Sale2

Create a Supplier

ActionIn the docs only

Adding a vendor becomes a side effect of your purchasing process: once a supplier is approved elsewhere, this action writes it into PHP Point of Sale.

When to use it
buyers validate new vendors in a form or a shared sheet and the store needs the same list.
Watch out
a vendor approved twice is created twice, so check with Search Suppliers before this step.
PHP Point of Sale3

Create an Employee

ActionIn the docs only

Onboarding gets shorter when a new hire appears in the store staff list as soon as HR records them in its own tool.

When to use it
a signed hiring form or an HR spreadsheet row should give the new team member a record in PHP Point of Sale.
Watch out
staff records are sensitive, so test with Run once on a dummy entry before switching the scenario on.
PHP Point of Sale4

Create an Expense

ActionIn the docs only

Spending recorded elsewhere, such as a receipt photographed by a manager or a delivery logged as a receiving, turns into an expense in your store books.

When to use it
paired with Watch Receivings, or behind an expense form that staff already fill out.
Watch out
map only the values you trust from the previous module, since a wrong mapping writes a wrong expense each time the scenario runs.
PHP Point of Sale5

Delete a Customer

ActionIn the docs only

Removing a customer profile from PHP Point of Sale can follow a request made somewhere else, which keeps your list in line with what clients asked.

When to use it
a client asks to be removed and the request is logged in a form or a support tool.
Watch out
nothing in the doc says a deletion can be reversed, so treat it as final and point it at the exact customer returned by a search, never at a guess.
PHP Point of Sale6

Delete a Supplier

ActionIn the docs only

Vendors you stop working with can disappear from the store once purchasing marks them as closed in its own tracker.

When to use it
a supplier contract ends and the list at the counter should no longer offer that vendor.
Watch out
the doc mentions no way to restore it, so add a filter before this module and run it once on a test supplier.
PHP Point of Sale7

Delete an Employee

ActionIn the docs only

Offboarding closes cleanly when the staff record leaves PHP Point of Sale the moment HR confirms a departure in its own system.

When to use it
a departure form is signed and the person should lose their place in the store staff list.
Watch out
assume it cannot be undone and double-check that the employee passed in is the right one, ideally found by Search Employees just before.
PHP Point of Sale8

Delete an Expense

ActionIn the docs only

An expense entered by mistake, or cancelled in your accounting tool, can be removed from the store books without opening the back office.

When to use it
a refund or a cancelled purchase order means the matching expense should go.
Watch out
treat a deletion as final; if you only need to correct an amount, Update an Expense is the safer choice.
PHP Point of Sale9

Get a Customer

ActionIn the docs only

This module fetches the full profile of one customer you already know, so later steps can use details the trigger did not carry.

When to use it
a sale or another app points to a customer and you need the rest of the profile before sending a message.
Watch out
it returns one record only; when you do not know which customer to target, start with Search Customers.
PHP Point of Sale10

Get a Supplier

ActionIn the docs only

Pulling one vendor record into the scenario lets you reuse its details, for instance in an email to purchasing or a row in a shared sheet.

When to use it
a receiving or a purchase request mentions a supplier and the next step needs that supplier's full record.
Watch out
Get a Supplier works on a supplier you can already identify, while Search Suppliers is the one to use when you only have a name.
PHP Point of Sale11

Get an Employee

ActionIn the docs only

Reading a single staff record gives the rest of the scenario the details it needs about one team member, without exporting the whole list.

When to use it
a shift tool or an HR form refers to an employee and you want their store record before updating anything.
Watch out
keep an eye on where that data goes next, since staff details should only reach tools your team is allowed to use.
PHP Point of Sale12

Get an Expense

ActionIn the docs only

One expense from your store, read in full, can be checked or copied into accounting before anyone approves or corrects it.

When to use it
an approval flow needs the recorded expense in front of the manager who signs it off.
Watch out
this reads one expense you already point to; to list several expenses, reach for Search Expenses, which may return many bundles.
PHP Point of Sale13

Make an API Call

ActionIn the docs only

Anything the listed modules do not cover can still be reached: this module calls any endpoint of the PHP Point of Sale API with the connection you already set up.

When to use it
the job you have in mind touches something outside customers, suppliers, employees and expenses, and the API exposes it.
Watch out
you write the request yourself, so keep the vendor API documentation open and test with Run once.
PHP Point of Sale14

Search Customers

SearchIn the docs only

Finding customers by what you know about them, before you create or change anything, is the job of this search, and it often saves you from duplicates.

When to use it
a signup arrives from your website and you want to know whether that shopper already exists at the register.
Watch out
a search can return zero, one or several customers, and each result is a separate bundle for the next module.
PHP Point of Sale15

Search Employees

SearchIn the docs only

When a request names a team member but carries no store reference, this search locates the matching staff records for you.

When to use it
before Update an Employee or Delete an Employee, to be sure you act on the right person.
Watch out
two people can match the same criteria; handle the case of several results, or of none, before the next step.
PHP Point of Sale16

Search Expenses

SearchIn the docs only

Pulling a set of expenses out of PHP Point of Sale lets you total them, export them or flag the odd one in another tool.

When to use it
your accountant asks for the expenses matching a condition and you would rather send a sheet than dig by hand.
Watch out
many matches mean many bundles, and every module after the search counts an operation for each of them.
PHP Point of Sale17

Search Suppliers

SearchIn the docs only

Checking whether a vendor is already on file takes one step with this search, which returns the suppliers that match your criteria.

When to use it
right before Create a Supplier, so a vendor approved twice in your buying process still has a single record.
Watch out
an empty result is normal and means no match; plan what the scenario should do then, instead of letting it stop silently.
PHP Point of Sale18

Update a Customer

ActionIn the docs only

Changes made in another tool, like a new phone number captured by your CRM, flow back into the customer profile at the register.

When to use it
your marketing or support team edits contact details in their own app and the counter should see the same data.
Watch out
find the customer with a search first, then check in Run once that only the details you meant to change were overwritten.
PHP Point of Sale19

Update a Supplier

ActionIn the docs only

Vendor details kept current in purchasing, such as a new contact or address, reach the supplier record in PHP Point of Sale.

When to use it
a supplier sends updated contact information and buyers log it in a shared sheet or form.
Watch out
updating the wrong vendor overwrites good data, so identify the supplier through Search Suppliers or Get a Supplier first.
PHP Point of Sale20

Update an Employee

ActionIn the docs only

A promotion, a new phone number or a role change recorded by HR can be copied onto the staff record in your store.

When to use it
HR keeps the master staff file elsewhere and PHP Point of Sale should mirror it.
Watch out
run the scenario once on a test profile, because a mapping mistake repeats on every employee the flow touches.
PHP Point of Sale21

Update an Expense

ActionIn the docs only

Correcting an expense after the fact, when an invoice shows a different amount or a better description, happens here without deleting anything.

When to use it
your accounting tool confirms the final figures and the store record should match them.
Watch out
point the module at the expense returned by Search Expenses or Get an Expense, never at a hard-coded record.
Need help

Need help automating PHP Point of Sale with Make?

A person reads every message.

FAQ

PHP Point of Sale and Make: common questions

01Is the PHP Point of Sale Make integration free?
Yes, on the Make side. PHP Point of Sale is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans drop the interval to 1 minute and remove the cap on active scenarios. You still need an active PHP Point of Sale account; see the vendor pricing page for that subscription.
02What do you need to connect PHP Point of Sale to Make?
An active PHP Point of Sale account and an API key. To get the key, open Store Config in your store, scroll to the bottom of the page, click Add API Key and copy the key displayed. Then add a PHP Point of Sale module in Make, click Create a connection, give it a name if you like, and paste the key. That single connection is reused by every module of the app.
03Do PHP Point of Sale triggers in Make work in real time?
No. No instant trigger is listed for this app, and the four Watch modules for customers, receivings, sales and suppliers work as scheduled triggers. Make checks the app on the scenario's schedule, every 15 minutes by default, and handles everything new at that moment. On the Free plan 15 minutes is also the shortest interval; paid plans can go down to 1 minute. Records created between two checks simply wait for the next run.
04What if a PHP Point of Sale module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the PHP Point of Sale API with the same connection, which covers what the 25 listed modules do not, such as data beyond customers, suppliers, employees and expenses. You write the request yourself, so keep the vendor API documentation at hand. Keep in mind that the Make doc page for this app says it was generated with AI, so confirm important details with PHP Point of Sale.
05Should you use Make or n8n for PHP Point of Sale?
It depends on your criteria. In Make you get 25 ready modules for this app, a visual editor and a guided connection with an API key, which suits teams that want to start from ready-made bricks. Many apps also have an n8n node, so check whether one exists for PHP Point of Sale before comparing. Then weigh the modules available on each side, how your team likes to build, and which tool already runs your other automations.
Same platform

Other docs you might need on this stack.

Browse all integrations