How do I connect Shopify to weclapp?
Products, orders and inventory need to match. Assess the existing integration and avoid duplicated work across your store and ERP.
AI-generated image- 1Quick answer
- 2Key takeaways
- 3Is there an existing integration between Shopify and weclapp?
- 4Which data should I map before connecting the systems?
- 5Why do product codes and variants matter so much?
- 6Why is my Shopify inventory wrong despite the integration?
- 7How do I avoid duplicate orders and shipment messages?
- 8What should I test before going live?
- 9When should I consider PrestaShop instead of Shopify?
- 10How can sjmedia help with the integration?
- 11Sources & further reading
- 12Cite this article
- 13Authors & technical review
Quick answer
weclapp offers a Shopify integration. Before setup, map products, variants and warehouses and assign responsibility for changes. Check the transfer direction for each data type and test orders, repeated processing and exceptions before using the connection in production.
Shopify takes orders while weclapp handles purchasing and inventory. Yet your team still copies orders manually or corrects products after import? The connection between the two systems deserves a closer look. The key question is which data should go where, and which system is allowed to change it.
At sjmedia, we start this assessment with a complete order workflow. From the item sold to the shipment notification, each step needs a clear owner. Successfully connecting the accounts is only the beginning.
Key takeaways
- Map products, variants and warehouses before the first sync.
- A bidirectional connection does not mean every field transfers in both directions.
- Test repeated order processing and exceptions in an isolated environment.
Is there an existing integration between Shopify and weclapp?
Yes. weclapp describes a Shopify integration supporting product master data, stock levels and the import of store orders, among other functions. Checking this existing connection is a sensible first step before commissioning custom development. What matters is the functionality and requirements of the integration you actually use, rather than the word “bidirectional” on a product page.
Bidirectional does not mean every field should be edited freely in both systems. An integration may transfer product data in both directions while using fixed directions for other records. Ask to see what it reads, writes and does when changes conflict, separately for each data type. An automatically imported order does not prove that returns are fully automated as well.
Which data should I map before connecting the systems?
For scoping and configuration, we recommend a short mapping document based on real examples from your catalogue. It helps distinguish a configuration task from a requirement for additional development.
- Products and variants: Which identifier links the same sellable variant in both systems?
- Descriptions and images: Which system may overwrite existing store content?
- Inventory and warehouses: Which weclapp stock figure belongs to which Shopify location?
- Orders and payments: At what stage should an order be imported and processed?
- Shipping updates: Who creates shipment information and who notifies the customer?
- Cancellations and returns: Which steps does the integration support, and which remain with your team?
These are requirements to check, not a promise that every function is included in the connector. For established stores, we pay particular attention to existing product pages. Internal inventory descriptions are not necessarily the copy customers should see.
- Identify data
- Define ownership
- Test transfers
- Check consistency
Why do product codes and variants matter so much?
A blue T-shirt in size M is a different sellable item from the same design in size L. If only parent products are matched, an imported order may appear correct while referring to the wrong stock item. We therefore check individual variants and the identifiers and product codes the actual integration uses.
Consider a simplified example: a retailer lists an item as “AB-104-B” in the store and “AB104B” in the ERP. Both make sense to a person. Whether the connector matches them depends on its mapping. This is an illustrative example, not a documented client case. It shows why importing a small set of known products can be more useful than approving a full catalogue transfer immediately.
Why is my Shopify inventory wrong despite the integration?
First check whether both systems are referring to the same quantity. Shopify distinguishes between stock that is on hand, available and committed, among other states. Products can also be held at multiple locations. Total inventory is therefore not necessarily the quantity available for new online orders.
For the connection, we define which system determines sellable stock and how reservations, blocked goods and returned items should be handled. We then compare one specific item before and after an order. The last successful sync and any transfer errors also matter. Making another manual adjustment in the store can hide the cause instead of resolving it.
When several sales channels are involved, the underlying inventory rules need a separate assessment. Our article on synchronising inventory between an ERP and an online store covers that topic. Here, the focus is on proving that those rules work in the specific Shopify–weclapp connection.
How do I avoid duplicate orders and shipment messages?
Before the first import, agree on the date from which orders should be transferred. An uncontrolled historical import can bring previously processed orders back into the workflow. A second connector or a manual import that is still running can cause similar problems when it transfers the same orders.
At sjmedia, acceptance testing therefore includes a repeat-processing check. If an interrupted run processes the same test order again, it must not create another shipment order. The connection needs reliable duplicate recognition. Its implementation must be checked in the actual connector. We also assign responsibility for shipping emails and status updates so that customers do not receive conflicting messages from several systems.
What should I test before going live?
One straightforward purchase is not enough. Also test a variant product, a discount, a cancelled order and a returned item in an isolated test environment. If partial shipments or multiple warehouses are part of your operation, cover those cases too. An unsupported exception needs a documented manual workflow before automation starts.
Acceptance also means establishing who notices a failure. We recommend a named owner, understandable logs and an agreed response to orders that stop progressing. Ongoing support should be settled alongside initial configuration. Access, installation and a green connection indicator alone do not make an adequate acceptance record.
When should I consider PrestaShop instead of Shopify?
If Shopify supports your sales workflows well, a sound weclapp integration is usually the logical next step. Connecting an ERP is not, by itself, a reason to replace a store. The decision changes when you are also planning individual B2B processes, specific ordering logic or extensive customisation within the store.
As a PrestaShop agency, we then assess PrestaShop as a flexible foundation for those requirements. Its documented Webservice API provides a technical starting point for integrations. A suitable connector, the actual workflow implementation and ongoing maintenance are still necessary. PrestaShop does not automatically make an ERP integration cheaper or maintenance-free. Our article on connecting PrestaShop to an ERP explores that decision in more detail.
How can sjmedia help with the integration?
We first establish whether the issue sits in your store data, the mapping, the transfer or the workflow that follows. This creates a specific scope for assessment and implementation: configure an existing connection, clean up data or develop an additional function. We coordinate ERP-side questions with the team responsible for that system.
When supporting your Shopify store, we also consider the impact on product pages and order processing. Bring an example of an affected product and an anonymised order workflow. That gives us a much more useful basis for identifying the next step than a general request to “synchronise everything”.
Sources & further reading
- weclapp: Shopify-Integration ↗accessed
- Shopify: Inventory states ↗accessed
- Shopify: Inventory and locations ↗accessed
- PrestaShop: Webservice API ↗accessed
Cite this article
Attila Tóth (sjmedia GmbH, Kuppenheim): How do I connect Shopify to weclapp?. 19 Nov 2026. https://www.sjmedia-consulting.de/en/wissen/schnittstellen/shopify-weclapp-verbinden
Author & technical review
Related to this topic.
Questions about this topic? Let’s talk about it.
I’ll listen to your situation and discuss which next steps suit your store.




