We have upgraded the MetaKocka system for transferring orders and recording payments. The purpose of the upgrade is to simplify order transfer and remove errors caused by missing payment method mappings.

Before:

With the setting "Payment transfer - customized" , all payment methods had to be mapped manually.

If a payment method was not mapped, the order was not transferred to MetaKocka. This could cause:

• errors when transferring orders,

• missing orders in MetaKocka,

• extra manual work checking and setting up mappings.
  
   

Now:

When transferring orders, MetaKocka now automatically checks whether the payment method already exists and is mapped for any of the other stores in your company.

If the payment method already exists, MetaKocka automatically copies the existing mapping to the store where the payment method is not mapped yet.

If the payment method does not exist yet, MetaKocka maps it accordingly. This way, orders with this payment method can be written to MetaKocka normally the next day.

What does this mean for the user?

Users no longer need to map every new payment method manually for every store.

The system takes care of the mapping and makes sure orders can be transferred to MetaKocka normally.

Goal of the upgrade

With the upgrade, we want to achieve:

• no order transfer errors caused by missing payment mappings,

• no missing orders,

• less manual work with settings,

• automatic handling of new payment methods.

• 
  

The change makes order transfer to MetaKocka more reliable and automated.