API Integration - Customer Internal Reference

Alright, here's how we use the glossary:

1. Product - a collection of multiple similar offers (usually the same service, with multiple tiers). Example: Microsoft 365.

2. Offer - a specific service within the product. Often represents a certain tier. Example: Microsoft 365 E3.

3. Subscription - what the customer has to use the service after the purchase. E.g. a subscription to Microsoft 365 E3. Subscription to a one-time offer is still a subscription, but it's invoiced once and doesn't renew. Multiple orders can relate to the same subscription (e.g. one order for when it was purchased, a few more for when it was changed, one more for when it was suspended).

4. Order - something that executes a purchase or a subscription change. The same order can relate to multiple subscriptions at once. Example: when you have multiple offers in the cart and click "place order", it will create one subscription for each offer in the order.

As you can see, an order is just a container for actions users perform with the subscription. Subscriptions are the more meaningful of the two, and they are the only ones that are invoiced. Orders that change the subscription just affect the amount in the invoice, but the invoice line is still for the subscription.

So does it seem like subscriptions are most synonymous with your "business case"? If so, I would suggest you save the reference number under the subscription.

Hi Igor,
I'm a little confused - what is the difference between subscription and order in this case.
We are going to sell both subscriptions (some cloud services for certain period) and prospectively products or services (one-time order).
��� Will solution suggested below be versatile enough?
��� Will it be possible to place multiple subscriptions per order?
��� Will it be possible to combine subsections and services on one order?
We are working closely with Nadya Tuleyko.
Best regards,

Jan Cervenka
Sales Operations Manager

[dns_logo_claim_rgb]
M: +420 703 433 956 ��� jcervenka@dns.cz
DNS a.s. ��� City Empiria ��� Na Str��i 65/1702 ��� 140 00 Praha 4
www.dns.cz

Sounds like you are talking about a new purchase scenario, so there's going to be one reference per subscription (not per order, because each subscription usually has a purchase order and many change orders for each time users reconfigure it). If this sounds right, I would look into using PO numbers:

1. When subscriptions are initially created, they can have a custom PO number (so, per subscription). It will also show up in the invoices next to the subscription they belong to.

2. If the subscription doesn't have its own PO number indicated, invoices display the default PO number from the contract under which the customer purchased the subscription. My guess is this aspect is not relevant to you, as your the references you want to save vary more dynamically.

Am I on the right track? Then we can look into the end-to-end integration you want to build and see which APIs to point you to.

Is anybody from our customer success or support team already helping you in any way?

Hello Igor,

Thanks for your reply. We will connect the AppXite platform with our CRM (Microsoft) so that each order generates an opportunity in CRM. This opportunity ID is the identifier we would like to assign to all products in the order, even if it includes multiple vendors.

Best regards,

Jan ��ervenka
Sales Operations Manager

[dns_logo_claim_rgb]
M: +420 703 433 956 ��� jcervenka@dns.cz
DNS a.s. ��� City Empiria ��� Na Str��i 65/1702 ��� 140 00 Praha 4
www.dns.cz

Hi, thanks for your request! What is the nature of the internal ID you want to save? Internal offer identifier, PO number, customer agreement number? Based on its nature and how you intend to use it later, should it be one per offer, per subscription?

Thanks for your answers in advance. We have a few ways of doing these things, so let's choose the right one together.