Importing Purchases

    Content of this article

    1. Preliminary Remarks
    2. Importing WBZ Dealer Purchases

    1. Preliminary Remarks

    WBZ dealers do not appear directly as buyers via the plenigo Checkout.
    Purchases are mapped in third-party systems and can also be transmitted to plenigo as an externally-managed offer.
    No individual purchases are mapped in the WBZ dealer account.

    2. Importing WBZ Dealer Purchases

    To carry out an order of an offer for WBZ dealers, it is required to import the order via the API.
    The corresponding endpoint or request is described in the API documentation.

    Note:

    Even though an order is technically imported, no order data is displayed in the WBZ dealer account. 
    Merely the subscriptions resulting from the order are displayed. 
    Customer Data
    To carry out the import, the WBZ dealer for which the order is created must have already been created in plenigo.
    If this is not the case, the WBZ dealer must be created via an additional request before the import. Follow the following steps:
    • POST-Request for creating a customer data set
    • Required data in the request:
      • email
        the email address of the customer as unique identification mark of the data set 
      • language
        the customer's language
    • The other fields can optionally be filled in.

    Import Data
    Required data in the request for carrying out the import:
    • externalSystemId
      Unique ID from the leading third-party system, which is marked at the order and subscription in plenigo.
    • plenigoOfferId
      The plenigo offer ID to be used
    • invoiceCustomerId
      The plenigo customer ID
    • quantity
      The desired number of the offer
    • startDate
      The start date for subscriptions. Determines the start date for the access rights in plenigo. 
    • paymentMethod
      The payment method that was used for the order. 
    In addition, further data fields are available. A complete list of all of them can be found in the API documentation.

    All imports are logged in the import log. 

    Note: An order import is carried out asynchronically. In the response to an import, a promiseId may be issued, which can be used for identification.
    Published