SAP Business One & Zuper Integration
A SAP Business One and Zuper integration keeps your ERP and your field service platform in sync — customers, equipment, contracts, and inventory flow from SAP B1 into Zuper, while completed jobs, quotes, and service updates flow back. We design, build, and support it end to end, using the orchestration approach that fits your workflow instead of forcing you into a fixed template.
Why Integrate SAP Business One with Zuper?
Field service businesses run on two systems that don't naturally talk: SAP Business One holds the commercial truth — customers, pricing, stock, invoicing — while Zuper holds the operational truth — jobs, technicians, schedules, site data. Without integration, your back office re-keys every job, and your technicians work from stale customer and inventory data.
Integration closes that gap. Dispatchers schedule against live ERP data, technicians see accurate equipment history on site, and finished jobs turn into SAP B1 documents without anyone touching a keyboard twice. For a service business running hundreds of jobs a month, that's dozens of admin hours recovered weekly and invoices that go out days sooner.
What Can You Sync Between SAP B1 and Zuper?
You can sync every core entity a field service operation depends on: business partners, service calls, equipment cards, items, warehouses, service contracts, and sales orders. Direction and triggers are configured per entity to match how your teams actually work.
| SAP Business One object | Zuper object | Direction | Typical trigger |
|---|---|---|---|
| Business Partners (OCRD) | Customers & properties | B1 → Zuper | Create or update |
| Service Calls (OSCL) | Jobs (work orders) | Bi-directional | Creation & status change |
| Customer Equipment Cards (OINS) | Assets | B1 → Zuper | Create or update |
| Items (OITM) | Products & parts | B1 → Zuper | Master data change |
| Warehouses (OWHS) | Technician & truck stock | B1 → Zuper | Scheduled sync |
| Service Contracts (OCTR) | Service contracts | B1 → Zuper | Create or renewal |
| Sales Orders (ORDR) | Approved quotes / completed jobs | Zuper → B1 | Quote approval or job completion |
| A/R Invoices (OINV) | Invoices | Configurable | Job completion |
Directions above reflect the most common configuration. If your field team creates new customers on site, we add a reverse flow for business partners; if billing lives in Zuper, invoices flow the other way. The mapping bends to your process, not the reverse.
Which Fields Sync Between SAP B1 and Zuper?
Field-level mapping is agreed and documented before we build anything. These are the standard mappings we implement per entity — the layer where templated connectors usually run out of road.
Business Partners → Customers
OCRD → Customers & properties
Card Code, name, billing & shipping addresses, contacts, payment terms, customer group. Ship-to addresses become Zuper properties so jobs land at the right site.
Service Calls ↔ Jobs
OSCL ↔ Work orders
Call/job cross-references, subject, customer & equipment, priority, status, technician, scheduled dates, resolution notes. Zuper status changes write back to the B1 call.
Equipment Cards → Assets
OINS → Assets
Manufacturer & internal serials, linked item code, customer reference, install date, warranty/contract linkage. Technicians see full asset history before arrival.
Items → Products & Parts
OITM → Products/parts
Item Code, description, unit of measure, price list values, per-warehouse stock. Parts consumed on a Zuper job deduct from the right B1 warehouse.
Warehouses → Truck Stock
OWHS → Stock locations
B1 warehouse codes map to Zuper stock locations, including van stock modeled as individual warehouses. Van inventory finally matches SAP.
Sales Orders & Documents
ORDR → Orders / invoices
Document & due dates, customer reference, line items with quantities, unit prices, warehouse codes. Completed jobs create B1 sales orders ready to invoice.
Beyond the standard set, we map user-defined fields (UDFs), job photos and attachments, and custom checklists — the layer where templated connectors usually run out of road.
How Do We Build the SAP B1 & Zuper Integration?
We build it one of three ways, chosen at scoping based on workflow fit, volume, and budget. Zuper exposes a modern REST API with webhooks; on the SAP B1 side we work through the Service Layer (HANA, and SQL on v10+) or the DI API for older SQL deployments.
| Approach | When it's right | Trade-off |
|---|---|---|
| Pre-built connector template iPaaS B1↔Zuper templates | Your workflow matches the standard entity set and you want the fastest go-live | Ongoing subscription; limited flex on custom fields and logic |
| Orchestrated iPaaS build Make, n8n + both APIs | Standard core plus custom rules, approvals, or a third system in the flow | Modest platform cost; needs a partner to own it |
| Custom middleware Service Layer + Zuper API/webhooks | High volume, complex transformation, on-premise constraints, no per-month platform fees | Higher build cost; you'll want our support retainer |
Here's the honest version: if a vendor template covers 100% of your requirement, buying it is the right call — and we'll configure it for you. Most field service businesses we scope sit at 80% standard and 20% custom, and that 20% (UDFs, approval steps, van stock logic, photo handling) is exactly where an orchestration partner earns their fee.
What Does the Workflow Look Like After Integration?
A typical order-to-cash cycle runs like this once the integration is live — no re-keying, no stale data, no invoice sitting in a paper folder for a week.
Log the call
A breakdown comes in; the office logs a service call in SAP B1 against the customer and their equipment card.
Create the job
The integration creates a matching Zuper job within a minute — customer, site, asset history, and priority attached.
Dispatch
Dispatch assigns a technician in Zuper, who sees service history and confirms parts from live van stock.
Complete & write back
The technician logs parts, captures photos and a signature, and closes the job; status and notes write back to the B1 call.
Bill same day
Parts post against the correct B1 warehouse and a sales order or invoice draft is created in SAP B1 for same-day billing.
How Long Does It Take, and What Does It Cost?
A standard SAP Business One and Zuper integration goes live in 3 to 6 weeks and costs between $4,000 and $15,000 depending on approach and entity count. Template-based configurations sit at the low end; custom middleware with UDF mapping and bespoke logic sits at the top.
| Scope | Timeline | Investment |
|---|---|---|
| Template configuration (standard entities) | 2 – 3 weeks | $4,000 – $6,000 + platform subscription |
| Orchestrated build (standard + custom rules) | 4 – 6 weeks | $7,000 – $12,000 |
| Custom middleware (full bespoke) | 6 – 10 weeks | $12,000 – $15,000+ |
Every quote is fixed-price after scoping. The mapping sheet you sign off is the contract for what syncs.
Field Service Integration Is Our Specialty
Connecting SAP Business One with Zuper is a flagship part of our integration practice. We understand both sides of the sync: the ERP objects (service calls, equipment cards, warehouses) and the field service reality (dispatch, van stock, on-site data capture). We build the standard flows fast and handle the custom 20% — UDFs, approvals, photo and checklist handling — that off-the-shelf templates can't.
Need the rest of your stack connected too? See our full SAP Business One integration services for ecommerce, CRM, payments, and more.
Frequently Asked Questions
Zuper doesn't ship a native SAP B1 connector. The integration runs through middleware: a vendor template, an iPaaS workflow, or custom code against both APIs. That's the layer we build and support.
Yes. On-premise B1 connects through a secure agent or exposed Service Layer endpoint over VPN or TLS. We handle the network configuration as part of the build.
Yes. We use the Service Layer on HANA (and SQL from version 10) and the DI API on older SQL deployments.
Yes. B1 warehouse quantities sync to Zuper stock locations, including van stock modeled per technician, on a schedule or near real time.
Yes, in either direction. Most clients generate the invoice in SAP B1 from the completed Zuper job; some invoice in Zuper and post summaries back to B1. We configure whichever owns billing.
Every flow includes retry logic, duplicate protection, error logging, and alerting to a named inbox. Failed records queue for review rather than silently disappearing.
Yes. Job attachments and custom checklist data can post to the B1 service call as attachments or UDF values — a common gap in off-the-shelf templates.
Yes. We audit the existing configuration, fix the mapping or replace the approach, and take over ongoing support.
Connect SAP Business One and Zuper the Right Way
Your ERP and your field service platform should act like one system. A properly scoped SAP Business One Zuper integration gets you there in weeks, with fixed pricing and a mapping sheet you approve before we build.