WeClapp

The remaining interface of WeClapp can be connected via wemalo-connect. The steps and information required for this are listed below.

Create client in wemalo

The client is created in wemalo in the usual way. For the client’s other facilities in wemalo-connect, the client ID and the warehouse ID must be known.

Create user in wemalo-connect

A new shop user is created in wemalo-connect and linked to the previously created client in wemalo using the client ID. The warehouse ID is also stored.

The creation of a REST-Key is not necessary!

Set up WeClapp interface

The WeClapp interface is created in the “Generic REST Interfaces” area. These interfaces use wemalo’s REST interface to communicate with the back end. However, the creation of a remaining token is not necessary.

A new interface can be defined by clicking on the “New entry” button. After selecting the system, the configuration of the system can be loaded via the button “System-Template”. Using the WeClapp example, key-value pairs are loaded for storing the required settings (URL, token, WeClapp ID, etc.). An overview of the required settings follows in the next subchapter.

You can also select the wemalo instance (previously set up by linking wemalo and the client ID) and the synchronization interval.

A warehouse must be created via Settings- >Basic settings- >Warehouse.
As soon as this is done you can open the warehouse via the edit function (pen symbol) and see the warehouse ID in the browser bar at the end (entityId=XXXX).
This is required in the WeClapp settings.

 

WeClapp Settings

The following settings must be provided by the customer:

  • Token: here you have to enter the token from the WeClapp shop, (My settings- > API Token) which has to be created.
  • url: the URL to the API interface of WeClapp. (Shop URL/webapp/api/v1)
    Example: https://4elements.weclapp.com/webapp/api/v1
  • (WeClappId: 1)
  • (storageLocationId: 1)
  • warehouseId: the ID of the warehouse in WeClapp.

 

The following settings are made by us:

  • extendedLog: true must be entered here to activate extended logging.

 

subscriptions

The following subscriptions can be activated/deactivated:

  • serviceLoadProducts: load product master data from WeClapp and transfer to wemalo.
  • serviceLoadGoodsOrders: load WA orders from WeClapp and send them to wemalo.
  • servicePushPackages: return sent packets from wemalo to WeClapp.
  • servicePushInventoryBookings: Transmission of inventory entries (entries and withdrawals).
  • servicePushIncomingBookings: Transmission of incoming goods bookings
  • servicePushSentBookings: Transmission of outgoing goods bookings.
  • servicePushReturnBookings: Transmission of return bookings.

 

Annotations

Due to API limitations, the following tasks must be performed manually in the shop.

In order to successfully create a delivery of an order, the order must be confirmed by clicking manually.

The dispatch of the delivery and the creation of the invoice must also be confirmed here by a manual click. The stock is not updated until the delivery was shipped.

The return of the order cannot be generated until the delivery has been sent.

The goods from the returns can be posted back to the warehouse by selecting “Post all items to warehouse” under “Goods receipts and workflow” in Weclapp.

 



Shopify

The Shopify REST API is integrated into wemalo-connectand connects Wemalo to the Shopify shop system.

Settings in Shopify

For the connection an API key, password and URL are required.

Under Apps- >Manage prive apps- >Generate API credentials the API access can be set up.
For example, you can assign wemalo-connect as the app name. After the key generation we need the API key, the password and the exact URL. Under “Example URL” there is a link with all the information you need, if you could send it to me, it would help us a lot. Here is an example:
The required access rights can be seen here:
Set up api
The required access rights currently include the following requirements:

Supported actions

  • Loading product Master Data
  • Loading orders
  • Transmission of sent parcels
  • Transfer of stocks

Product master data

  • products for which requires_shippinghas not been set are not loaded.
  • All other products/variants are synchronized. SKU, EAN, weight, name, product group and manufacturer are exchanged.
  • Please note: the SKU (also in variants) must be unique.

Attention: A known bug on the part of Shopify is that Shopify does not change the external ID of duplicated products. This is necessary to transfer a new products to wemalo.

commissions

  • Orders with the financial_status paidand fulfillment_status unshippedare loaded and the Wemalo_Downloadtag is set.
  • Order header data, delivery address and items are synchronized.
  • The note field can be used to specify a pick info.
  • In order to determine the correct shipping service provider, Wemalo queries the name of the selected service provider. To match, this must be stored in Wemalo as an external ID for the profiles to be used.
  • Only positions for which “requires_shipping” has been set are transmitted to Wemalo.
  • Note: once an order has been submitted to Wemalo, no further changes to the order will be submitted to Wemalo.

Transmission of packages/tracking numbers

  • The tracking number is transferred back to Shopware together with the shipping service provider.
  • This automatically changes the fulfillment_status.

Transfer of stocks

  • In order for a Wemalo inventory to be transferred, the Inventory Policymust be activated.
  • Wemalo does nottransmit negative stock if there are incomplete orders that cannot be served. Otherwise the variants can no longer be called in Shopify.
  • Only pickable stocks are confirmed. I.e. goods on blocked stock or already picked goods will not be transferred as available stock to Shopify.

Find out Location ID

  • In the shop, go to Settings (bottom left), then click on the Locations area.
  • Then select the default location.
  • The location ID can then be seen in the address bar of the browser (e.g. 1112222122).

If the Location-ID is not correct, a hidden Location-ID can be determined by wemalo. This is done via the REST call.



shopware

Shopware is integrated into wemalo-connect and can be used to exchange data with Wemalo. In wemalo-connect a shop account is necessary.

The supported versions and functions are listed in the function matrix.

Settings in Shopware

  • Set up API users in shopware
  • API user, API key and URL to Shopware’s rest API are required.
  • After the initial setup, Wemalo sets all stocks to 0!*1

User setting shopware

Configuration in wemalo-connect

  • a shop user must be set up
  • for the interface Shopware the data from the previous section must be entered
  • The synchronization time can be set. If the time is set to 0, the interface is off.
  • The individual data subscriptions can be activated/deactivated
  • For each data subscription, the system records when the subscription was last successfully completed.
  • The interface shows when the interface was last executed.

products

  • All activeproducts are loaded and transferred to Wemalo.
  • Only products that have updated since the last successful product synchronization are considered.
  • The product ID is stored in Wemalo as an external ID and is used to match the product master data.
  • The article number from the shopware is transferred to Wemalo as SKU.
  • The weight is read in as kilograms, product dimensions as centimetres with decimal places.
  • For variant articles, the additional text in shopware is appended to the name in Wemalo. It is therefore necessary to fill this field, for example, with the color or another text so that a distinction can be made between the different variants in the warehouse.

orders

  • Orders with the status “In process (Waiting)” are downloaded by Wemalo and set to the status “Ready for delivery”.
  • After dispatch, orders are set to the status “completely delivered”.
  • The matching of the shipping service provider to be used is done via the name of the stored shipping type, e.g. standard shipping”.
  • Note: once an order has been submitted to Wemalo, no further changes to the order will be submitted to Wemalo.

Via wemalo-connect invoices can be downloaded as Base64. To do this, the end point must be stored in the wemalo-connect shopware configuration under “Invoice end point”. In addition, the Shopware API must be extended by the stored end point.

wemalo assumes that the base64 document about {“data”: {“pdfDocument”:”base64 “}} can be retrieved……..

stock

  • Current product inventories are loaded via wemalo-connect and synchronized with shopware. Only pickable stocks are confirmed. I.e. goods on blocked stock or already picked goods will not be transferred as available stock of shop goods.

Sent parcels

  • The tracking code is transferred to the order in shopware. If an order is shipped in several packages, the tracking numbers are separated by semicolons.
  • The order is then marked as sent.

returns

  • An order status can be stored in Wemalo that is used for picking up registered returns (e.g. “Register returns”). If Wemalo has loaded a return, the status is set to “Wemalo fetched”. Both status IDs are not available in the standard shopware and must be newly stored in the shopware.
  • It can also be activated that returns are reported back. In addition, the retrieval of returns must also be activated, since Wemalo requires the ID of the order to retrieve the returns message. An accepted return is displayed in Shopware on the basis of another new status.

*1: Excluding products

If products are not to be synchronized, they must be assigned to the customer group WAPI (Wemalo API). To do this, a new customer group must first be created in Shopware:

Create customer groups

The customer groups must then be assigned to the products that are notto be called up by Wemalo:

Assign customer groups

Please note: The assignment must take place before Wemalo loads the product!

 



wemalo-connect Release

Version 1.2.3

Date: 13.11.2017

Version 1.2.2

Date: 14.09.2017

  • Shopware configuration simplified
  • Activating/deactivating of wemalo instances implemented
  • new rest call for creating inventories implemented

Version 1.2.1

Date: 17.08.2017

  • Loading return orders from Shopware and pushing back booked returns integrated

Version 1.2.0

Date: 16.08.2017

  • Integration of Shopify api
  • Enhancements to shopware api

Version 1.1.0

Date: 07.07.2017

Version 1.0.1

Date: 28.06.2017

  • new call for creating multiple products at once added to connect api
  • possibility to set a product as activated/deactivated added to connect api
  • new rest calls need wemalo-backend 1.5.2.1 or later

Version 1.0.0

Date: 09.06.2017

  • connect-api has finally been implemented
  • wemalo-connect now allows using a wemalo rest api to transmit product data and goods orders and to load information about stock changes and sent packages
  • the api needs wemalo-backend 1.4.4 or higher

Version 0.2

Date: 07.06.2017

  • additional rest calls implemented
  • rest calls are now being validated before sending them to wemalo
  • preparation for managing shop systems in wemalo-connect

Version 0.1

Date: 31.05.2017

  • first beta version of wemalo-connect has been released
  • in this version it’s possible to manage users, wemalo instances and to communicate with wemalo via a rest api


wemalo-connect

wemalo-connect wemalo-connect connects Wemalo to shops, ERPs and other external systems. The software can be used independently of Wemalo, e.g. to synchronize the WordPress shop with the Plentymarkets shop. In addition, wemalo-connect provides a REST API to Wemalo, which is used to exchange product master data, transmit orders and query inventories. The full range of functions can be seen in the interface documentation: connect-api