Skip to main content

Recording orders in your systems

Once an order is approved and you are receiving topi's webhooks, you record it in your own systems, whether that is an ERP (such as SAP or Microsoft Dynamics), accounting software, or your ecommerce backend. This page covers the one thing that matters when you do: who your customer is, and how to represent topi.

Who is your customer?​

When an order arrives from topi, you face an important question: is your customer the business buying your products, or topi?

Legally, topi Asset GmbH is your customer, and the business that placed the order (the "end customer") has a rental contract with topi. Even so, we recommend you record the end customer as the customer in your systems, and record topi only as the payment method on the offer and order. Two reasons:

  • Customer sovereignty. Your customers stay exclusively yours, with topi acting as the financing provider for the rental.
  • Analytics. Recording every topi order against topi would make it impossible to analyze your own customers.

How to record it​

Whatever system you use, the mapping is the same. Using an ERP as the example:

  • The end customer stays the customer, and the rented devices are associated with their profile.
  • topi is the billing address (this is always the same).
  • topi is the payment method linked to the offer and order.
  • Store the topi offer id in a field of your own, so you can reconcile later. It is returned by createOffer, for example 739b63c2-9e58-4964-b38d-4ebb424de242.

On fulfilment, the goods ship to the end customer and the invoice goes to topi. So:

  • Invoice recipient (Rechnungsempfänger) = topi Asset GmbH
  • Recipient of goods (Warenempfänger) = end customer
  • Ordering party (Auftraggeber) = end customer
  • Payer = topi Asset GmbH

In your ecommerce store​

The order should still be visible to the end customer in their "My Account", "My Profile", or equivalent, so they have a transparent overview of their orders.