MATJRAH DEVELOPERS + APPS CENTER

Publish your system
integration on Matjrah.

Register as a vendor or implementation partner, create a public or private app, test it in Sandbox and submit it for review. Each merchant approves the scopes and receives an independent installation.

Start in the Developers Center Meet the Partnerships team

Integration support: dev@matjrah.com · Shipping integration guide · llms.txt

THE MATJRAH PLATFORM

One platform for online stores, customer apps and POS.

Matjrah manages orders, products, inventory and customers across sales channels. The Developers Center provides the API, Webhook contract and Sandbox; Apps Center manages publishing and installation.

Partners do not share one global key across customers. Each merchant approves explicit scopes and receives an independent, revocable access token.

3,500+merchants use Matjrah

3 sales channelsOnline store, customer app and POS

Per-store installsIndependent scopes and access token for each merchant

2 publishing pathsPublic catalog app or private invite-only app

Dynamics 365

Examples of systems a vendor or implementation partner can connect—not a claim that an official ready-made app exists for every brand.

24-HOUR SANDBOX SCOPE

One order event, SKU mapping and one safe API write.

Self-service Sandbox proves installation and signed sample-event delivery; it is not a merchant store, subscription or admin login. Gateway reads/writes require a provisioned active test store. Understand the environments ↗

CHOOSE THE INSTALLATION MODEL

Three clear integration paths.

A public app for many merchants, a private app for one store, or dashboard API and Webhooks for a merchant-managed integration.

01 / PRODUCT VENDOR

Build once, serve many merchants

An ERP provider turns its connector into a discoverable public catalog app instead of starting a new custom project for every store.

Public app path →

02 / IMPLEMENTATION PARTNER

Connect one store with clear boundaries

An agency or developer creates a private app, binds it to the store domain and sends an invitation the merchant reviews and approves.

Private app path →

03 / OPERATIONS TEAM

Know which system owns each decision

The store owns the commerce experience and order; the operational system owns its internal processes. The integration moves change without creating a sync loop.

Read the runtime contract →

THE COMPLETE PRODUCT — NOT ONLY AN API

From integration idea to merchant-ready app

The Developers Center provides the documentation, build workflow and testing environment. Apps Center manages publishing, invitations and per-store installation. APIs and webhooks become the runtime after the merchant installs your app and grants its scopes.

01Register as a partnerOne account for your integration team.
02Create the appChoose public or private distribution.
03Select scopesRequest only the orders, products or stock access you need.
04Test in SandboxProve signed events, then certify APIs on an active test store.
05Submit for reviewProvide clear data handling and safe behavior.
06Distribute and monitorUse a public listing or private invitation.

CHOOSE YOUR APP MODEL

Two distribution paths in Apps Center

Both use the same app contract, a separate installation for every store and explicit scopes. What changes is who can discover and install the app.

PUBLIC APPFor many merchants

Public catalog app

For ERP, accounting and inventory providers that want a reusable integration discoverable and installable by multiple Matjrah stores.

A public listing in Apps Center
Review and approval before publishing
Separate installation, scopes and access token for each store
Designed for SaaS and multi-customer partnerships

Read the public ERP app guide ↗

PRIVATE APPFor one store

Invite-only private app

For an agency or implementation partner building a store-specific connection while keeping approval, scopes and installation inside Apps Center.

Not listed in the public catalog
Bound to a specific store domain
Delivered by invitation and approved by the merchant
Revocable without sharing the store's master API key

Read the private app guide ↗

THE RUNTIME LAYER

APIs and webhooks power the installed app

Start with an initial REST API import, consume signed events as changes happen, then call the API for the required read or update. Make every consumer idempotent and protect it from duplicate events and synchronization loops.

01 / ORDERS

Orders

Read order lists and order details, then update status with an optional comment when granted.

02 / PRODUCTS

Products

Read products, create new disabled products and update only the fields your app sends.

03 / INVENTORY

Inventory

Read the declared stock owner and safe total, then update the exact product, legacy option value or managed variant.

04 / WEBHOOKS

Signed events

Order, product and stock events use HMAC signatures and a request_id for deduplication.

05 / CUSTOMERS

Customers

Read registered customer master data and order, refund and net totals for reconciliation.

06 / FINANCIAL FACTS

Payments and documents

Read payment state, issued invoices and notes, structured refunds and merchandise returns through separate scopes.

Open the complete API reference ↗ 120 requests / minute / installation

SYSTEMS A PARTNER CAN CONNECT

From global ERP suites to custom operations software

A vendor or implementation partner can build a Matjrah app for these systems and many others. They are integration examples—not a claim that an official ready-made app exists for every product listed.

Odoo

SAP Business One

SAP S/4HANA Microsoft Dynamics 365 Business Central Oracle NetSuite Zoho Books Custom ERP / WMS / POS

REVIEW READINESS

An integration merchants can trust and operate

Review does not begin with your logo or listing copy. It begins with data ownership, least-privilege scopes, failure handling and traceability for every installation.

Least privilegeRequest only the scopes required by the real workflow.
IdempotencySend a stable idempotency key for every retryable write.
DeduplicationStore request_id and ignore events already processed.
Tenant isolationNever mix access tokens, queues or logs across installations.
Actionable monitoringCorrelate failures to the installation and request without exposing secrets.

START THE RIGHT PATH

Build independently, or plan the integration with us.

Start with the Developers Center guides. If you represent an ERP vendor or need technical and commercial alignment, schedule a conversation with our Partnerships team. For integration support, email dev@matjrah.com.

Explore developer guides Book a 30-minute call