Shopify weclapp integration

weclapp behind you. Shopify in front.For brands with mixed B2C and B2B business that use weclapp for inventory management and do not want to maintain the store separately.

When the combination is worth it

weclapp is a cloud-based inventory management system from the German-speaking market that pulls order processing, warehousing, CRM and accounting preparation into one system. For brands running B2C and B2B side by side that is a realistic scope, and the reason why the Shopify connection is rarely only about products and stock.

weclapp offers a documented programming interface and connection options for store systems. The actual work lies in deciding which fields the store takes over from the ERP and which ones it leads itself. That boundary decides whether marketing can work in the store or against the next sync run.

Which objects sync in which direction

Product master data and documents belong in the ERP, presentation and the customer account in the store. Additional fields are best placed in Shopify as metafields.

Object	Direction	Leading system	Note
Products	→ Shopify	weclapp	Product number, units and additional fields from weclapp, texts stay in the store.
Inventory	→ Shopify	weclapp	Available quantity after reservation, calculated per warehouse.
Prices	→ Shopify	weclapp	Sales prices and customer conditions from weclapp.
Orders	Shopify →	Shopify	Shopify creates the order, weclapp takes it over for processing.
Customers	↔ both ways	Split by field	Created in the store, customer number and assignment in weclapp.
Fulfillments	→ Shopify	weclapp	Shipping and tracking from weclapp back into the Shopify order.
Credit notes	→ Shopify	weclapp	Credit note in weclapp, refund via Shopify.

Which integration pattern holds up

Directly via the weclapp interface
The documented programming interface covers the relevant objects. A lean custom service in between is often enough to translate formats, log the runs and make errors repeatable.
iPaaS for several channels
As soon as marketplaces or a logistics provider hang off the setup alongside Shopify, an integration platform is worth it. It gives everyone involved the same view of runs and errors, at an ongoing cost.
Custom middleware
The usual route when B2B conditions, sales representative logic or additional fields have to be represented. The translation between the ERP model and the store model then sits in one place and can be tested, instead of being scattered across connector settings.

Typical pitfalls

Additional fields with no destination
Additional information maintained in weclapp needs a defined counterpart in Shopify, usually a metafield with a fixed definition. Without that schema the values end up in free text fields and are useless for filters and templates.
B2B and B2C in the same price field
Net prices for business customers and gross prices for consumers cannot be represented in a single standard price. For B2B the route runs through Shopify catalogs and price lists, otherwise the wrong group sees the wrong figures.
Overwriting texts
If the sync sets product descriptions from the ERP, marketing loses its work on every run. It makes more sense for weclapp to supply only structure and facts and for Shopify to lead on the communication.

Frequently asked questions

How is weclapp connected to Shopify?

Through the documented programming interface that weclapp provides, either with an integration platform or a small custom service in between. What decides the outcome is less the tool itself than the agreement about which system holds the truth for which field.

Can B2B customers see their conditions in the store?

Yes, through Shopify company profiles with their own catalogs and price lists, filled from the weclapp conditions. Which volume tiers and customer prices can be transferred cleanly belongs in the discussion before implementation, because not every type of condition has a direct equivalent.

Where do additional fields from the ERP belong?

Into Shopify metafields with a fixed definition, not into description texts. Only then can they be output in templates, used for filters and compared again later on. The schema should be defined before the first sync run, not repaired afterwards.

Which system leads on inventory?

weclapp, because goods receipt, reservation and picking are booked there. Shopify only displays the available quantity. What matters is that reserved goods no longer count as available, otherwise the store keeps selling stock that has already been promised to someone else.

Does accounting cope with this automatically?

Documents are created in weclapp, but the handover to accounting is a separate step. The reconciliation of payment providers in particular, covering payout, fee and timing, needs its own concept and does not fall out of any store integration as a by-product.

Shopify Xentral integrationFor D2C brands outgrowing spreadsheets that want to run order processing, warehousing and shipping in one place at last.View integration Shopify JTL-Wawi integrationFor retailers who run their operations in JTL-Wawi and want Shopify as the sales channel in front, instead of changing systems again.View integration Shopify DATEV integrationFor merchants who want their Shopify revenue posted cleanly into financial accounting, without expecting DATEV to hold products or inventory.View integration

System integration: patterns and data ownershipThe overarching view of ERP, PIM, WMS and middleware.Blankroast Manufaktur Case Study