ERP integration
Bring your SAP B1Bring your NetSuiteBring your DynamicsBring your AcumaticaBring your UnleashBring your ERPWe’ll make it work.
Pepperi’s iPaaS connects to the systems you already run, from ERP and accounting to inventory, payments, BI, and other back-office tools. MOD.fyi maps the data, joins the sources, tests the rules, and supports the integration after launch.
Pepperi · Your ERP
Pepperi and your ERP, moving together.
Your ERP stays the system of record. Pepperi is the clean selling layer in front of it. MOD.fyi owns the mapping, connection, testing, and support path between them.
Your ERP
System of record
What MOD.fyi owns
Mapping. Testing. Exceptions. Support.
Configured by us, supported by us, while you’re a customer.
Pepperi
Order layer
What the integration carries
ERP objects, in detail.
The integration supports any object the ERP exposes via API or SQL. The lists below are the most-asked-about. Bring custom fields to the discovery call and we’ll confirm field-level mapping.
Into Pepperi · Read from ERP
Master data, pricing, inventory, and commercial state
Items, customers, contacts, brand & category hierarchy.
Price lists, customer pricing, contracts, promotions, UOM.
Stock per warehouse, allocations, in-transit, lot & batch.
Invoices, AR balance, credit limits, payment terms, order history.
Product images, attributes, kits, bundles, mixed-pallet rules.
Back to ERP · Write to ERP
Orders, payments, customer changes, and field activity
Sales orders, kit & bundle expansion, allocation flags.
Cash on delivery, check, ACH, credit-card auth & capture.
New accounts, address & contact updates, credit-limit asks.
Returns & credit memos, RMA reasons, restock fees.
Visit notes, signatures, photos, service tickets.
Supported integrations
Your ERP is on the list. Or it isn’t, and we still connect.
Eight named ERPs we ship every month, plus the ones we configure for customers running something custom. If your system has an API or SQL access, we connect to it.
Your ERP, too.
API or SQL accessIf it exposes either, we’ll integrate. We’ve done it across 30+ ERPs over a decade.
Built to integrate
Any ERP, any WMS, any well-defined endpoint.
We treat the integration layer as a first-class product, not a one-off engagement. These are the protocols we ship over.
REST / OpenAPI
Modern JSON APIs.
SOAP / XML-RPC
Legacy enterprise endpoints.
Direct SQL / ODBC
Read straight from the database when there's no API.
Flat-file / EDI / SFTP
Scheduled drops. EDI 850 / 810 / 856 / 997.
Webhooks & event streams
Real-time push from the ERP.
GraphQL
Selective queries on richer ERPs.
AR & payment gateways
Pepperi runs on your gateway, not ours.
Some implementations bury you in payment fees by forcing their processor of record. We integrate with whichever gateway you’ve already negotiated — your rate, your terms, your AR posting back to the ERP. Same approach we take with the ERP itself: it’s yours, not ours.
Cards, ACH, and Stripe Terminal in-person.
Card processing and eCheck — the long-running default.
PayPal, Venmo, and cards through Braintree.
Your processor, too.
CardConnect, NMI, Cybersource, Worldpay — if it exposes a gateway API and you’ve already worked out your rate, we wire it up.
How the work moves
Project path, in six steps.
Map and Shape are the methodology. Connect, Test, Launch, and Own are how Shape and Own play out in time. Total length depends on ERP complexity and customer readiness.
01
Map
Work with you to understand the operation. Orders, reps, buyers, warehouse, pricing, ERP. Pattern-match to known archetypes.
02
Shape
Configure to match. Rules, workflows, UOM, approvals, promos, cutoffs, data shape.
03
Connect
Build the integration. Map ERP objects, build sync, exception handling, audit trail.
04
Test
Validate with users. Pilot a small set of accounts and reps. Catch edge cases early.
05
Launch
Cut over and train. Go-live window, rep + back-office training, monitor closely.
06
Own
Support and improve. First-line support, configuration changes, continuous fit.
Ready to get specific?
We can scope the ERP, the rules, the data, the gateway, and the launch path.
Bring your ERP, your channels, your processor, and your current order entry method. We'll bring the questions.
Map. Shape. Own.