pixi

Using several Clients in pixi

Using several clients / shops describes the possibility, to maintain your companies, business units, online shops, sales channels or seperate customers in pixi*.


When does it make sense to seperate Clients?

Common scenarios are:

  • You want to use pixi* in different companies.

  • Items get distributed between parent company and subsidiaries.

  • You run different online shops/sub shops with seperate store views.

  • You also sell items in outlets and/or on trade fairs.

  • You are connected to different marketplaces (e.g. Amazon, ebay, Zalando).

  • You run different accounts in one multichannel system (e.g. Afterbuy, Tradebyte, Brickfox).

  • You want to seperate B2C and B2B customers.

  • Your customers consist of key accounts with individual requirements.

  • Sales representatives are part of your staff and should be evaluated individually.


Back to top

Single Database - Advantages and Possibilities

Bank and Paypal Import with different Accounts

In case you use different bank accounts for your clients, you can assign an appropriate booking account to each bank account.

For this you need to enable the database setting "Mapping of bank accounts to bookkeeping accounts" (pixi* Control Center > Database Settings > Payments > DATEV export). In case payments get imported from an unknown bank account, pixi* asks for the related booking account. If you set the booking account once, pixi* won't ask for it next time you do the import.

Since you can set up only one PayPal account using the PayPal API, you need to enter the related booking account into the "Account Number for PayPal Import" setting in pixi* Control Center.

If you use several PayPal accounts, you should import payments using the "PayPal Zahlungsabgleich" app which you can book in the pixi* Apps Marketplace. This app can handle several PayPal accounts and you can assign booking accounts to each PayPal account. Payments and the related booking account are then imported to pixi* using the pixi* API and they are included in the DATEV export.

Read more:

Back to top

Templates for Invoices, Slip Pages and Credits per Client

On automatic invoice printing (also applies to slip pages and credits) pixi* automatically uses the invoice template which is assigned to the shop to ensure the corporate identity of your shops.

Requirements are:

  • Either name the templates so they match the shop ID, e.g. "DEM.rtm", "AKM.rtm", "MAD.rtm", ... or

  • Use printing rules to assign an appropriate template to each shop (renaming is not needed in this case). Printing rules also enable you to assign templates using additional criteria such as location, shipping country, order type, etc.

Read more: Invoice Templates

Back to top

Seperate Range of Invoice Numbers per Client

You can define a seperate range of invoice numbers for each shop. You can further define, which invoice number should be the first one, how many characters an invoice number should have and whether the invoice number should have a prefix and which one.

Like this you can precisely define invoice number formats and easily see at a glance, which shop the invoice belongs to.


Back to top

Configuration of Auto E-Mails per Client

All automatic e-mails can be configured to have different layouts for each shop. In case such an e-mail gets created, pixi* automatically checks which shop is assigned to the order/invoice and uses the appropriate template for creating the e-mail.

You can also define a shop for e-mails that are manually sent in pixi* Customer Service. Like this you always know which e-mails were sent to customers of which shop and the possibility to send e-mails containing the wrong layout or text are minimized.


Back to top

Seperate Sender Information on Label Creation

You can set a sender reference for shipping vendor DHL for every shop. The sender reference is included in the polling file created by pixi* and gets checked by the shipping vendor software. It then assigns the sender reference to the appropriate client accordingly.

Your customers then always know which shop the package they received came from and returns might be prevented.


Back to top

Separate or DATEV Debtor Export across all Clients

Using the Accounting Export App 2.0 you can export debtors separated by shop or you can also export them across all shops. Als invoices and payments can be exported per shop.


Read more: pixi* Accounting Export App 2.0

Back to top

Overall or seperate Analysis for Clients

By default pixi* already offers a large number of evaluation possibilities that can be checked per shop or across all shops.

Some reports that can be checked per shop are:

  • Invoices/Credits

  • Turnover by Payment type

  • Customer Orders For Period

  • Not Paid Invoices List

  • Turnover by Items

  • Gross Profit

Sample screenshots for those reports:

"Invoices/Credits" Report


"Turnover by Payment type" Report

"Customer Orders For Period" Report

"Not Paid Invoices List" Report

"Turnover by Items" Report

"Gross Profit" Report

Back to top

Using Clients with separate pixi* Databases

In some cases, it can be advantageous to use a separate pixi* database for every shop. For example, if you operate as a fulfillment provider separating item stock as well as orders from different shops. Working across databases works only partially.

Creating reports across different shops that have a separate pixi* database is not possible because the pixi* desktop applications always connect to one pixi* database. What you can do is export the needed reports for every shop as an Excel file and then merge them.

Another possibility is using the pixi* API. You can also get the needed data from the different databases using the pixi* API. Save them in the format which fits best and analyse them.

Read more:


Costs

You need to buy a client license as well as pay for the effort to set up this new client. This also applies in case you need a new database. For further information please contact your responsible Account Manager at ACCM@pixi.eu.

Back to top

Single Database or separate Databases?

Whether you should use one single database with different clients or one separate database per client can be hard to tell. This depends on different conditions. In any case, you should talk to pixi* to ensure finding the best possible solution.

The following table contains some advantages and disadvantages of having a single or separate database:

Topic

Single pixi* Database
with different Clients

Separate pixi* Database
per Client

Customer Service

  • access to all orders, invoice data, credits, customer accounts, e-mails allows central customer service as well as returns processing

  • every client only has access to its orders, invoice data, credits, customer accounts and e-mails

DATEV

  • identical range of DATEV account numbers for all clients

  • DATEV export per client possible

  • individual range of DATEV account numbers per database

  • clients can export DATEV files by themselves

Payment Import

  • payment information of all clients visible

  • payment import for all clients

  • payment information only visible for the specific client

  • payment import can be configured per client

Apps

  • all apps are booked for all clients, and no individual configuration

  • apps can and need to be set up for every database separately

Applications

  • no dedicated access and no individual management of permissions and roles per client to view only specific data

  • switching databases for customer service, payments, shipping, reporting is not necessary, no potential mistakes

  • access can be limited to specific applications and functionalities; like this clients can do specific tasks by themselves

  • switching databases is needed for all applications and (mobile) data processing devices

Other

  • easy update and maintenance for the (only) pixi* database

  • additional clients and channels can be set up easily and quickly

  • stock value reports can not be loaded per client in case locations are not used

  • item data can not be assigned to a single client in the standard range of functions, you can not search for items of a specific client

  • bigger flexibility and better overview when configuring automatic e-mails, invoice documents (printing rules) as well as templates for manual customer service e-mails

  • completely separated warehouse areas which allows to load a stock value report for every client

  • item tags can be configured individually per database and match the clients requirements

  • deliveries, stock movements and shipments need to be processed separately, working across clients is not possible


Back to top