Multi Warehouse

Inhaltsverzeichnis

Introduction

With this external PepperShop module, multiple warehouses are available in the shop. This makes it possible to record and manage multiple stock levels per article.

The module itself focuses in the current version mainly on stock management. Before using the module, certain processes may still need to be implemented if the standard solution does not fit – e.g. selection of the warehouse to be debited on order receipt and display of warehouse data in the article detail view (possibly with sub-articles).

Module Configuration

First, go to the Multi Warehouse module management: Main menu of ‘Shop Administration’ > ‘Modules’ > ‘Multi Warehouse’ (see screenshot excerpt on the right).

In the Multi Warehouse module management, click on the “Configuration” button at the very top. Now you reach the configuration mask of the Multi Warehouse module. Here you can activate the module and see usable warehouse locations (see: ‘Warehouse Definition’).

Figure 1: Configuration part of module management

Module Activation

Activation: Set a checkmark in the checkbox here if this module should be activated. After the information has been configured accordingly, you should make sure that it has been saved (click on the ‘Save'-Button).

Warehouse Definition

The warehouses are defined in the configuration mask of this module. The management is quite simple and intuitive. Please be very careful with deleting a warehouse in live operation!

⚠ Warning: A change has very far-reaching consequences: All linked warehouse stocks and the history of the warehouse are affected.

Administration

The article field has autocomplete. The article must be selected from the autocomplete list, otherwise the form is considered incomplete. If there are already bookings for the corresponding article, these are displayed after selection via autocomplete. The cost center is the only field that is not mandatory. Below the form, the last bookings made are listed, so that with many bookings the overview is not lost.

General Configuration (when clicking on ‘Configuration’ button)

Figure 2: Multi Warehouse administration mask

  • Activation: Should the module be active?
  • List of usable warehouses (display): Info: New warehouses are only created or changed via shop database, as there are important dependencies. Best to edit via phpMyAdmin. For each warehouse you assign a designation (warehouse number). The warehouse ID is assigned by the shop system itself.

Warehouse Management

  • Configuration: Button leads to the configuration mask of this module.
  • Export warehouse list by date: Enter date here in format DD.MM.YYYY [HH:MM:SS] to export a warehouse overview. The CSV format readable via Excel / LibreOffice is used

Warehouse Booking

In this section, a warehouse operation is performed. Depending on where this mask was called from, the ‘Article’ field may already be pre-filled (GET parameter artikel_id. You can also just enter an article to see what its last operations looked like.

  • Article: Type the name of an article or its article number in the input field. The shop displays a Type-A-Head search result list from which you select the article to be edited. Info: As soon as an article has been selected, the shop displays an overview of the last Multi Warehouse operations with this article below the booking mask.
  • Warehouse: Here you can select from a list of existing warehouses. The warehouse booking operation then applies to this warehouse.
  • Action: Which warehouse operation should be performed?
    • Goods Receipt: Increase stock level of an article
    • Goods Issue: Decrease stock level of an article
    • Inventory (booking): Set stock level of an article
    • Transfer Warehouse Stock: If this option is selected, the shop displays a second warehouse selection. Now you specify from which warehouse to which warehouse you want to transfer the desired number of articles. Two operations are always booked: A goods receipt and a goods issue at the other warehouse.
  • Number of Articles: Please specify the desired number of articles to be booked here.
  • Cost Center: A booking note

The input mask can also be adjusted, see chapter Appendix 1.

Last Bookings

At the bottom you see a table with the last Multi Warehouse bookings across the entire article range and the navigation button to leave the mask. Orders are directly linked.

Import / Export of Multi Warehouse Data

The Multi Warehouse module is integrated into the PepperShop Import/Export tool of the Basic version. Thus, you can take over warehouse stocks as absolute values (inventory booking type) when importing into the shop system or also integrate them as data into the export output.

Selection of Columns for Export

Shop Administration – Import/Export – Import/Export Tool – Export Article Stock (click button)

In the now appearing list, the standard field ‘Stock’ is missing, instead the warehouses defined via Multi Warehouse module are listed with the prefix ‘Warehouse ‘, e.g. ‘Warehouse Hannover’ and ‘Warehouse Munich’. If you set a checkmark there, the shop will export the corresponding stock levels of the respective articles.

Article Import

Here simply upload and import an import file with the same export column names.

Integration in Article Edit Mask

Figure 3: Article info display at the very bottom in the article edit mask

If you edit an article via ‘Articles’ → ‘Edit existing article’, you see a warehouse info display and a button that leads directly to the warehouse edit mask. Sub-articles are also displayed here (see example image).

Booking on Order

If an order arrives via webshop or cash register1 and the shop is configured in warehouse management to directly perform warehouse bookings, this is automatically done according to the following rule (should be adjusted in shop/lager.def.php in correkt_lagerbestand_fuer _kunde(..) if needed):

  1. First debit from the warehouse with the highest stock of the article
  2. If a larger quantity is ordered than articles are in stock at the warehouse with the highest stock, there are multiple warehouse actions:
    1. Debit as many articles as possible from each warehouse with positive article stock
    2. Debit excess articles at the warehouse with:
      1. the largest article stock
      2. the largest reservations (outstanding stock) – if there were no articles in stock

Display of Warehouse Stocks on Customer Side

In the delivery state, visitors to the shop are only shown the cumulative (sub-)article stock. This information can be used as an exact number or as a traffic light (red, green) in the article list and in the article detail view. If a different display form is desired here, you can adjust this in the following method: shop/module/multilager/lager.def.php in get_lagerbestand_fuer_kunde(..).

A simple way to get a list with the warehouses and the stocks can be read as follows:

$lager = new lager.def.php();
$lager→set_artikel_id($artikel_id);
$lagerliste_array = $lager→get_lagerbestaende_des_artikels();

Installation

System Requirements

To use the Multi Warehouse module, at least a PepperShop v.6.0 Standard or Connect is required.

Copy and Upload Files

The Multi Warehouse module consists of some files and two directories that must be copied into your installed PepperShop. First, extract the provided ZIP archive. Essentially two directories must be copied:

{shopdir}/shop/Admin/module/multilager
{shopdir}/shop/module/multilager

The files can be easily uploaded to the web server via FTP or SCP. The placeholder {shopdir} stands for the shop directory on the web server, where among other things the file index.php together with README.txt can be found.

Module Installation

After copying the files, you can go to the shop administration and switch to the menu* ‘Modules’* there. On the left side, with the not yet installed modules, you now see the Multi Warehouse module listed.

Figure 4: The Multi Warehouse module is listed (modules may vary)

Now the Multi Warehouse module must be selected and the ‘Install’ button clicked. If the installation routine runs without problems, this is communicated on the following page. The module is now installed. We now click on the button ‘Back to Module Management’ and there ‘Back to Module Administration’. We now see a button for the Multi Warehouse module. If you click on this button, the administration of this module appears.

The installation of the Multi Warehouse module is now complete. For the module to be used, the module must now be adapted to the specific configuration of the shop operator, see the next chapter Module Configuration, further below.

Activate Warehouse Management

In the shop administration, you must now activate warehouse management via ‘Articles’ → ‘Warehouse Management’ → ‘enabled’ → Save. The Multi Warehouse is also already linked in this mask.

Compatibility

This module is currently not compatible with the warehouse synchronization of the PepperShop module Synchronization Tool (matching of master data between multiple PepperShops to form a shop network).

Help / Open Questions

For open questions, the PepperShop forum is available:

http://www.peppershop.com

Appendix 1: Advanced Configuration: Administration Mask

Calling the Mask with Pre-selected Data

The mask for bookings of articles can be configured. There are call parameters that can be transmitted as GET parameters, so that the mask can be adjusted:

This mask can be called with pre-selected data. For this you can use the following GET parameters:

  • lager_id = Pre-select a warehouse here. For this, lager_id must be specified as GET parameter with the numeric warehouse ID value. This value can be read from the configuration mask.
  • lager_id_2 = Pre-select a target warehouse here. For the Transfer action, two warehouses must be specified. Here you can select the target warehouse. For this, lager_id_2 must be specified as GET parameter with the numeric warehouse ID value. This value can be read from the configuration mask.
  • lastkonto = Define the pre-selected cost center here
  • anzahl = Enter a pre-selected quantity. Warning: If the quantity is pre-selected, the action is executed immediately after entering a valid article identification!
  • in_popup = Should the mask be rendered without navigation options (e.g. in a PopUp?), then simply append &in_popup=true.
  • aktion = Define the pre-selected action of the mask here, e.g. the following:
    • ein = Record goods receipt
    • aus = Record goods issue
    • um = Transfer warehouse stock
    • inv = Inventory (overwrite warehouse stock with new value)

Example call of a goods issue mask:

http://www.example.com/shop_pfad/shop/Admin/module_admin_aufruf.php?darstellen=4&installed_selection=multilager&backlink=6&in_popup=true&lager_id=2&lastkonto=2003&aktion=aus

Mask Configuration

In the following PHP file there are several control constants with which you can influence the behavior of the mask for entering warehouse bookings. This is particularly important when using a barcode scanner and the manufacturer module, since here you define the database field of the barcode field (MULTILAGER_ARTIKEL_IDENT_FIELD = 'artikel_code'):

define('MULTILAGER_MAX_ANZ_LETZTE_BUCHUNGEN' , 10);
define('MULTILAGER_ARTIKEL_IDENT_FIELD' , 'Artikel_Nr');
define('MULTILAGER_JUMP_TO_FIELD_AFTER_IDENT_FILL', 'anzahl');
define('MULTILAGER_COPY_ANZAHL_FELD_AFTER_COMMIT' , false);

Further Help

Do you have questions or need assistance? Do you have special requirements or desire a custom solution for your system? Our support team is happy to help. Support services are charged based on time and material at CHF 195.- / hour. Here is how to reach us:

Other Useful Pages


  1. PepperShop POS, the web-based cash register solution: https://www.peppershop.com/pos/ ↩︎

🌶️
🔥
🌶️