The following data is required to connect Weamlo to the DPD cloud service:

• UserCredentials CloudUserID
• UserCredentials Token
• if not yet available, please contact ci@dpd.de – lasts approx. 1 day

In Wemalo, shipping profiles are created under Configuration- >Shipping profiles. A shipping account should also be set up for DPD to store the above information. Subsequently, shipping profiles can be stored referencing the account, e.g. for the different shipping products of the provider.

• Your EKP number
• Login and password for the DHL business customer portal. Please create a new user for us.
• The product “Send” must already be activated for you. If you have any questions, please contact your DHL contact directly.

In Wemalo, shipping profiles are created under Configuration- >Shipping profiles. A shipping account should also be set up for DHL to store the above information. Subsequently, shipping profiles can be stored referencing the account, e.g. for the different shipping products of the provider.

Wemalo supports the Magento Rest-Api in Magento 2.

Setup

To do this, a remaining user must be created in Magento that has extensive authorizations. Wemalo accesses at least the following resources:

• POST V1/shipment/track
• POST V1/shipment
• POST V1/order/{id}/invoice
• GET V1/invoices?searchCriteria[filter_groups][0][filters][0][field]=order_id&searchCriteria[filter_groups][0][filters][0][value]={id}
• GET V1/products/{sku}
• GET V1/products?searchCriteria..
• GET V1/orders?searchCriteria...
• POST V1/invoices/%s/capture
• POST V1/invoices/%s/emails
• POST V1/shipment/{shipmentId}/emails
• PUT V1/products/{sku}/stockItems/{id}
• POST V1/orders/{salesOrderId}/comments

Create User Role:

• System -> Benutzerrollen -> Neue Rolle hinzufügen
• Role name e.g. wemalo
• Role Resources: Catalog, Shops, Data Transfer, Sales (Orders, Invoices, Shipments)

Create user:

• System – > All users – > Create new user
• Assign user name, first and last name and password
• Assign previously created user role
• username and password are required in the data exchange configuration in wemalo

Set Up Integration

• System – >Integrations – >Add new integration
• Only assign name and set authorizations analogous to user role
• release and store tokens in the data exchange configuration in wemalo

Define Order Status:

• Shops – > Order status – >Create new status
• Status code vendor, status label fulfillment
• Status code wemalo_ready, status label Ready
• Use “Assign status to status” to specify that wemalo_ready is to be used for payment input.

functional overview

• Loading of product master data
• Load customer orders (Note: once an order has been submitted to Wemalo, no further changes to the order will be submitted to Wemalo.)
• load invoices
• Transmission of sent parcels and tracking numbers
• Transfer of stocks
• Execution of invoicing and e-mail dispatch

Loading orders

• All orders with the status wemalo_ready (must be newly created in Magento) are downloaded by Wemalo. A comment is then added and the status is changed to vendor(also to be newly created).
• Note: once an order has been submitted to Wemalo, no further changes to the order will be submitted to Wemalo.

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

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:

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

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

Version 1.2.3

Date: 13.11.2017

• WordPress API implemented
• New REST Api calls implemented

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

• Shopware API has been integrated into wemalo-connect
• new rest calls for wemalo release 1.5.2.2 implemented, see api documentation

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

The refurbishment view can be used to scan serial numbers and set item characteristics. If the serial number is unique, the corresponding article is loaded immediately and its product and storage location information is displayed. If historical entries already exist, these are displayed.

If the serial number is not unique, the user is first shown a selection of the possible articles from which he can select one or scan a new serial number.

If historical entries already exist, these are displayed.

Optionally, the article can also be relocated directly by scanning a parking space barcode.

The individual steps are:

1. scan the serial number
   
2. Display of current parking space and history
   
3. Optional selection of new parking space, selection of attributes and saving

If the serial number cannot be found, a selection list is displayed:

This selection list would appear, for example, if there were the same serial number for different products, or if a serial number had been collected several times (as in the example above).

There is a Refurbishment module in the user master record. If it is checked, a new refurbishment entry appears in the menu below production poders. Refurbishment actions can be carried out using this mask.

Article characteristics can be created in the client master. The standard feature is intended for determining the condition, such as 1st choice, B-goods etc.. In addition, there is a characteristic Packaging to indicate the state of the packaging and a characteristic function, which can be set after a function test.

The standard feature is set directly when returns are accepted. It can also be changed during stock transfer and can be seen in the stock views.

The packaging and function features can be seen and changed via a special refurbishment mask. A technical employee can use this screen to set the corresponding characteristics and store a comment. The packaging feature can be set when scanning a return if the user is assigned the refurbishment module. However, it is not displayed in the position, but exclusively via the refurbishment mask.

The individual characteristic groups can be set via a corresponding selection box. The characteristics are all displayed in a mask for the client, but they are displayed grouped according to group in the table.

Each group can have a standard feature.

Version 1.8.1.4

Date: 23.10.2018

• reservation process splitted by client

Version 1.8.1.3

Date: 22.10.2018

• new auto report packaging material implemented
• loading goods order parcel information via rest call (via wemalo-connect)

Version 1.8.1.2

Date: 27.09.2018

• minimum dimension per sku (for clearing)
• new rest call for getting not synchronized bookings (GET and PUT)
• external article number added to available stock rest call
• system inventory: added product name and new overview with current stock, reserved stock and packed items implemented

Version 1.8.1.1

Date: 12.09.2018

• fix: Deutsche Post shipping label were not printed automatically

Version 1.8.1.0

Date: 07.09.2018

• new auto reports: goods order status and incoming stock report
• product unit names are now unique
• whitespaces removed from address fields
• mysql views removed and stock movements view optimized
• filter handling and dashboard queries optimized
• added a serial number check functionality
• fix: orders were set to packed even if block flag was set

Version 1.8.0.5

Date: 15.08.2018

• optionally executing services based on number of orders already sent
• executing inventory booking improved
• supporting placeholders in dispatcher profile ids
• fix: rest api: externalId and sku was mixed up in call product/getAll

Version 1.8.0.4

Date: 13.07.2018

• rest api: additional fields added to getSentPackages call
• rest api: returning back wemalos attachment id when adding a goods order document
• setting a parcel as finally packed when adding a tracking number

Version 1.8.0.3

Date: 10.07.2018

• loading goods receipt by order id filter adjusted (will now load related order only)
• information about number of palettes and boxes added to delivery orders
• fix: shipping label for Deutsche Post without postmark was not created anymore

Version 1.8.0.2

Date: 09.07.2018

• setting connection timeout to 3s when printing documents
• printing and creating shipping labels separated
• fix: typo in rest api fixed (deliveryNote instead of deliveryNumber when announing returns)

Version 1.8.0.1

Date: 05.07.2018

• fix: gsom is used for creating json from java classes. But in one case a class referenced it self what let in some situations to a stack over flow.

Version 1.8.0.0

Date: 04.07.2018

• creating of documents has been moved to a new application to minimize work load in wemalo backend
• using a service for sending emails instead of sending it from backend directly
• house number logic has been extended
• additional rest calls and webhooks (esspacially for Parcelito)
• fast send functionality introduced
• export customers email information for DHL Easylog, DPD Delisprint and GLS Gepard optionally
• fix: searching by ean2 and ean3 in product master data has been fixed
• fix: searching by ean when creating a goods order manually fixed
• fix: show products if client is activated only

Version 1.7.0.1

Date: 21.06.2018

• reservation strategy optimized

Version 1.7.0.0

Date: 03.06.2018

• new product units feature implemented (http://help.wemalo.com/gebindefunktion/)

Version 1.6.0.1

Date: 23.05.2018

• additional countries added to street/housenumber split functionality

Version 1.6.0.0

Date: 16.05.2018

• new feature shipping cost matrix
• possibility for ignoring a product while pick and pack implemented
• multiple enhancements and design optimizations
• changing an article from a product to a different one in refurbishment view provided
• added a warning weight property to dispatcher profiles

Version 1.5.5.1

Date: 28.03.2018

• fix: loading refurbishment entry by id fixed
• fix: don’t break auto reservation in case of picks

Version 1.5.5.0

Date: 06.03.2018

• auto report open orders extended
• aggregate sku information on relocate order view
• csv upload functionality for uploading tracking numbers as batch files
• setting weight limits for packing
• avoiding recreating shipping label if tracking number is already set
• issue a warning when total weight exceeds the max gross weight
• displaying serial number and lot for relocation view and stock view
• serial number and lot added to relocation
• trigger webhook for stock updates
• trigger refurbishment action webhook
• new calls for getting not synched return bookings and setting bookings as synchronized
• execute webhooks when delivery order was booked, returns and refurbishment hooks adjusted
• print settings added to print function

Version 1.5.4.5

Date: 21.02.2018

• deleting unused reservations in clean up call
• goods order information added to booked returns call

Version 1.5.4.4

Date: 12.02.2018

• refactoring and minor enhancements

Version 1.5.4.3

Date: 07.02.2018

• new field for charging customers added to refurbishment view
• lot information added to packing list

Version 1.5.4.2

Date: 31.01.2018

• options added to refurbishment view

Version 1.5.4.1

Date: 23.01.2018

• new call for adding notes to orders
• cell type added to stock overview
• creating serial number barcodes for returns
• option for skipping serial number check added to announced returns

Version 1.5.4.0

Date: 12.01.2018

• adding linked order id to rest call for announcing return orders
• trigger wemalo connect webhook on status update
• adding documents to return shipments implemented
• lot and serial number added to inventory

Version 1.5.3.12

Date: 04.01.2018

• generate package list after package was packed
• new rest call for getting list of available dispatcher profiles

Version 1.5.3.11

Date: 20.12.2017

• serial number unique check as customer option
• split house number and street for NL
• break auto reservation in case of relocations
• added price information to order position
• setting priority when creating an order

Version 1.5.3.10

Date: 12.12.2017

• setting blocked reason optimized
• split house number and street for DACH
• rate limiter added to reduce amount of parallel reservation bookings
• avoiding reimport of sent orders

Version 1.5.3.9

Date: 30.11.2017

• setting street and house number as required fields
• amount of reserved articles added to system inventory

Version 1.5.3.8

Date: 29.11.2017

• additional integration of lot management in picking, packing and returns processes
• ignore sent orders when importing an order via rest api

Version 1.5.3.7

Date: 22.11.2017

• if a picking list is being closed and has non-picked goods orders, those orders will no longer been canceled but moved back to open
• a picker doesn’t have access to close picking list button anymore
• lot management configuration integrated into client master data
• on packing view, already packed goods orders won’t be listed anymore

Version 1.5.3.6

Date: 20.11.2017

• show a waiting circle if creating a shipping label takes longer
• REST Api extend for loading refurbishment data by serial number only
• fix: if shipping label couldn’t be created, an order was blocked. That’s ok, but we missed setting the order status to blocked packed. This has now been adjusted.

Version 1.5.3.5

Date: 13.11.2017

• REST Api extended
• possibility for re-importing orders if already sent implemented
• adding reason for partially reserved to REST API
• new rest call for getting reduced stock information implemented
• lot management added to customer, lot start and end added to slim stock information call
• “forget” external goods order id if cancelled
• re-create order if updating an existing order and if order can be cancelled
• delivery note added to goods receipt api call
• added an additional check before closing stock orders

Version 1.5.3.4

Date: 18.10.2017

• Image to pdf converter implemented (used for directly printing Deutsche Post labels)
• generate package files if print service was activated only

Version 1.5.3.3

Date: 12.10.2017

• additional services added to shipcloud/dhl
• fix: grouping by carrier in price list fixed

Version 1.5.3.2

Date: 11.10.2017

• pick categories enhanced
• dispatcher product added to sent parcel calls
• check if return position was part of linked goods order
• option loading positions by sku instead of external id in rest calls integrated

Version 1.5.3.1

Date: 10.10.2017

• handover Deutsche Post parcels immediately if activated only

Version 1.5.3.0

Date: 03.10.2017

• bill export extended: services and pick categories were added

Version 1.5.2.19

Date: 28.09.2017

• external id added to product data when returning all products via wemalo-connect
• fix: mutli cient picking lists thrown an exception if there were no single client picking list…
• fix: path optimized picking didn’t recognize storage fields

Version 1.5.2.18

Date: 20.09.2017

• enhanced splitting of street and housenumber

Version 1.5.2.17

Date: 19.09.2017

• filter out dispatcher profiles by parcel weight
• adding name 1, name 2 and name 3 to Deutsche Post shipping label

Version 1.5.2.16

Date: 18.09.2017

• email added to csv export (GLS Gepard, DHL Easylog)
• purpose field for DPD COD extended
• additional services added to DHL Webservice (email notification, return receipt, visual age check)
• retry reservation if an error happened due to lock exception
• showing/hiding inactive users and clients, edit button not shown if goods order is cancelled
• loading stock movement data last 90 days by default

Version 1.5.2.15

Date: 12.09.2017

• provided additional logs when creating/updating a goods order via soap call failed

Version 1.5.2.14

Date: 11.09.2017

• log messages when changing from draft to partially didn’t work enhanced
• fix: setting to partially reserved if order is in status draft

Version 1.5.2.13

Date: 07.09.2017

• updating partially reserved orders enhanced

Version 1.5.2.12

Date: 01.09.2017

• don’t change goods order status to ready for packing of if order is not in status picking
• saving Deutsche Post Internetmarke request and response in case of an error
• using , instead of . in parcels weight (easylog csv export)
• default sender address data has been changed
• ready for shipment flag will now been set based on destination storage cell
• serial numbers will now been displayed on storage cells
• added a call for resetting goods order reservations
• check goods orders priority when reserving goods
• possibility to reserve goods by etd (goods will already been reserved, but goods order will stay in status partially reserved until etd has been reached).
• delete goods order reservations if partially reserved only and reservations on partially reserved was not activated
• fix: loading stock movements by storage cell didn’t work anymore

Version 1.5.2.11

Date: 24.08.2017

• when determining available goods, packing area will now also been counted
• new rest call for executing inventories (needs wemalo-connect update)
• booked return shipment orders will not be loaded anymore when entering a new return order
• database field for email addresses in end of day report set to text to allow more than 255 characters

Version 1.5.2.10

Date: 20.08.2017

• product group and serial number added to stock movement view
• stock movement search enhanced and changed from soap to rest call
• end of day report enhanced

Version 1.5.2.9

Date: 17.08.2017

• adding additional information to sent packages
• announce return position by sku allowed
• fix: when returning return position (external id and delivery note were mixed up)

Version 1.5.2.8

Date: 15.08.2017

• offering strategies for handling unknown products while importing new orders (skip position, create new, throw error)
• permission handling in rest service optimized

Version 1.5.2.7

Date: 08.08.2017

• new auto report end of day implemented
• possibility to send auto reports to multiple recipients as comma separated list implemented

Version 1.5.2.6

Date: 02.08.2017

• fix: search for picking list if picking box doesn’t contain picking list relation anymore

Version 1.5.2.5

Date: 31.07.2017

• booking history enhancements: product group and serial number are now being displayed, loading of history enhanced

Version 1.5.2.4

Date: 17.07.2017

• new call for getting all products via wemalo-connect implemented
• additional log entries added
• permission handling optimized

Version 1.5.2.3

Date: 10.07.2017

• negative stock implemented (products that were ordered but not on stock yet)
• save goods order status changes in separat history table to get an overview of status changes

Version 1.5.2.2

Date: 06.07.2017

• max values set to product dimension (max width=3m, max height=5m, max depth=3m)
• new rest calls for wemalo-connect:
  • getting available stock (including virtual stock)
  • getting a product by its external id
• Refactoring:
  • moved generic report creation from soap to rest
  • Obviously, pick quantity option was not read correctly (by wemalo-web). In the database it was set to 0, but it was as read as 1. So changing the values to fix this.
  • update virtual quantities after updating a product
  • search for active products only
• fix: when executing reservation for parts list: if executed automatically positions were not deleted before reservation started. This could result in duplicate positions. This has now been fixed.
• fix: pick by serial number didn’t select the one scanned, but by product and storage cell

Version 1.5.2.1

Date: 28.06.2017

• wemalo-connect now can create multiple products at once and change a products active flag
• wemalo-app integration
• fix: field cell name was not propagated correctly

Version 1.5.2.0

Date: 23.06.2017

• for new deliveries and returns with serial numbers a check has been integrated to proof, that neither sku/ean was scanned, nor the serial number is already on stock
• Since some scanners add whitespaces to serial numberes, serial numbers are now being saved without whitespaces
• displaying serial numbers in sent packages
• fix: new attributes packaging and functional were not saved in refurbishment view

Version 1.5.1.0

Date: 20.06.2017

• sending order package content to shipcloud in metadata field (sku, quantity, serial number if available)
• function to relocate products with serial numbers added to handheld/mobile view

Version 1.5.0.0

Date: 19.06.2017

• goods order positions and reserved articles refactored to optimize data loading
• product parts lists introduced
• bugfix: sometimes delivery notes were generated and printed twice

Version 1.4.4.1

Date: 12.06.2017

• filter extended in serial number view: it’s now possible to search by a serial number
• dhl express now added as shipcloud product
• it’s now possible to add a serial number to a goods order position manually
• bugfix: reserving goods order positions if new attributes packaging and function were added

Version 1.4.4.0

Date: 08.06.2017

• new refurbishment view and article attributes packaging and functional implemented
• product groups implemented and added to product search
• wemalo is now fully integrated in wemalo-connect
• new customer field allocation added

Version 1.4.3.3

Date: 06.06.2017

• wemalo-connect: Loading return shipment orders by external ID
• searching for products in product master data, creating incoming orders/goods orders and service allocation enhanced
• creating product parts lists
• Bug fix: avoiding null pointer exception if searching for an return without customer oder number

Version 1.4.3.2

Date: 31.05.2017

• when creating goods orders automatically, search product by sku if external id was not found