Cadmon Systems connects Priority ERP to your online stores, CRM, monday.com and AI agents through Priority's OData API, including custom forms and subforms. Orders, inventory, contracts and order changes reach Priority without anyone typing them in.
5
Priority environments in five countries, in one integration
2
Priority companies, in Israel and the USA, kept in sync
12
WooCommerce stores running on one Priority ERP
41+
Production scenarios in the 12-store project
In most companies Priority holds the orders, the inventory and the customers, and everything else gets there through someone typing. Store orders, contracts from email and changes approved over WhatsApp arrive late and with errors. An API integration closes the gap: your systems read from Priority and write to it on their own.
✕ Store orders keyed into Priority one by one
✕ Contracts and order changes entered by hand, separately for each company
✕ Every system holds a different version of the inventory
✓ Orders, inventory and customers sync with Priority automatically
✓ Contracts and changes arrive as drafts, and a person approves before the write
✓ Several Priority companies and environments update under clear rules
From reading and writing standard forms to running several Priority companies side by side.
We read and write standard and custom Priority entities, including nested subforms, through the OData API.
Orders, inventory, customers and documents move between the store and Priority with no typing.
One integration works across several Priority companies, such as an Israeli company and a US company.
Quotes, contracts and order changes prepared by AI reach Priority as drafts for approval.
Order changes run under control: a temporary status, the line update, the status restored, and the change mirrored between companies.
ERP advisory and Priority presentations for executive teams, before deciding what to connect and how.
We work in phases, and you see a result at every step before we move on.
01
A written document covering the process, the Priority fields, the routing rules and the edge cases, so everyone agrees on what gets built.
02
One complete flow runs in real conditions. A person approves the data before it is written to Priority.
03
We sit down with the person who owns the process and decide what works, what changes and what comes next.
04
We add templates, channels, companies or Priority environments, and you get clear documentation of everything we built.
The challenge: An Israeli manufacturer runs two Priority companies, LTD in Israel and INC in the USA. Every order change had to be updated in both environments, and approvals were scattered across email.
The solution: A change request opens in a monday.com form and moves to an approval board. Seven Make.com scenarios write the change to Priority through OData, across four change types: price changes go to LTD only, and date or quantity changes go to both companies.
Order lines in LTD and INC update together, and every request and approval is recorded on one board.
Every connection here comes from a project we delivered.
Orders, inventory and customers move between WooCommerce stores and Priority, as in the 12 stores of an importer and retailer.
Requests and approvals run in monday.com, and Priority updates after the approval.
DocuPipe parses contracts into fields, and Priority receives a draft for a person to approve.
Microsoft email works alongside Priority in request and approval flows, as in order changes between two companies.
Tranzila payments sync with Priority, as part of the order layer for 12 stores.
Every order in Priority gets a courier label, and the customer gets a tracking number.
A design for bringing a fashion retailer's product catalog into Priority through Boost.space.
The ways to connect Make.com to Priority ERP, and when each one fits.
More projects with Priority at the center, and the services that work with it.
Every order moves on its own from the store to Priority, to the courier label and to the customer's tracking.
Contracts in 25 to 30 templates reach Priority as drafts for approval.
Every project where Priority ERP is connected to other systems.
The layer that connects Priority to your stores, monday.com and AI agents.
Requests and approvals in monday.com, and Priority updates after the approval.
Five connected services: Make.com, business process automation, AI agents, Priority ERP and monday.com.
Can Make.com integrate with Priority ERP?
Yes. Make.com connects to Priority ERP through Priority's OData REST API, including custom forms and subforms. Cadmon Systems has built Priority integrations for orders, inventory, quotes, contracts and order changes across up to five Priority environments.
How do you connect WooCommerce to Priority ERP?
The most reliable way is an integration layer on Make.com that syncs orders, inventory, customers and documents with Priority via its API. Cadmon Systems connected 12 WooCommerce sites to one Priority ERP, including courier labels and tracking, in about 30 working days.
Can one integration work with several Priority companies or environments?
Yes. One integration can read from and write to several Priority companies and environments, with rules that decide where each record goes. For an Israeli manufacturer, price changes go to the Israeli company only, while date or quantity changes go to both the Israeli and the US company.
Can AI write data into Priority?
Yes, as a draft that a person approves. Document AI such as DocuPipe parses a document into fields, and Make.com writes them to Priority as a draft for approval. This is how a global automotive supplier brings in price contracts across 25 to 30 templates and five Priority environments.
How long does a Priority integration project take?
A typical integration project runs 4 to 8 weeks, and multi-phase AI programs take longer. A 12-store eCommerce integration with Priority went live in about 30 working days from the specification.
On a discovery call we map the systems that talk to Priority, and decide together what to connect first.
