The B2B Manager licensing framework enables tailored tier licensing based on your EDI business requirements. The licensing framework includes specific entitlements such as trading partners, EDI document types, EDI transactions, and VAN transactions. A tiered licensing model will allow users to access varying levels of EDI functionality based on their subscription tier.
Note
The B2B Manager license applies to the legacy endpoints and platform license type.
The overage policy is permitted for each EDI license component. It applies only to the platform license type and is limited to production environments (not Sandbox or non-production).
For more information on how to request access or upgrade your B2B Manager subscription, see Request access or upgrade to B2B Manager.
|
Tier name |
Number of trading partners |
Number of document types |
|
|---|---|---|---|
|
Basic |
3 |
5 |
High transaction volume cap (1000 transactions per month) |
|
Advanced |
10 |
5 |
|
|
Expert |
25 |
5 |
|
|
** Add-ons
**A trading partner is with whom you conduct business, such as a vendor or customer. |
|||
As per the above table, the below image shows a B2B Manager subscription with an Expert tier and add-ons.
-
If VAN, FTP, or AS2 connectors do not have an EDI profile configuration, they are counted under platform endpoints.
-
Each unique EDI profile is counted as a trading partner.
-
A trading partner with multiple business units, each having a unique identifier, results in separate EDI profiles.
-
Multiple EDI profiles may share the same name but will still be counted individually. Even if an EDI profile shares a name with others, each unique _ediProfileId is counted.
-
EDI profiles are not counted if:
-
The associated flow is inactive.
-
They are not set for any flow bubbles.
-
Example: Two trading partners using the single/same EDI Profile, the count is one.
-
One trading partner using two EDI profiles, the count is two.
-
-
Custom-created EDI profiles are applicable as individual trading partner counts.
-
The EDI profile count may differ from the trading partner count since multiple profiles can be created for a single trading partner.
-
Trading partners are counted separately for sandbox, production, and multi-environment entitlements.
-
EDI profiles created under VAN, FTP, and AS2 are counted as trading partners.
-
The document type is determined by the selected File Definition Rules (FDRs).
-
Variations of the same document type do not increase the count.
-
Functional acknowledgements are excluded.
-
Inactive document types are not counted.
-
A document type will not be counted if its corresponding flow is not active/enabled.
-
Multiple trading partner document types can be grouped/mapped into a single category, and counted as one document type.
-
Each category will have an ID for identification and management, similar to EDI trading partner and document-type IDs.
-
Document categories are counted separately for sandbox, production, and multi-environment entitlements.
The below table depicts the document types and how similar documents are grouped for counting purposes.
|
Entity/Category |
Doctype definitions grouped under entity |
Count |
|---|---|---|
|
Purchase order |
Walmart-4010-850-PurchaseOrder, Amazon-4010-850-PurchaseOrder, Sysco-4010UCS-875-PurchaseOrder |
1 |
|
Invoice |
Walmart-4010-810-Invoice, Amazon-4010-810-Invoice |
1 |
|
Ship notice |
Walmart-4010-856-ShipNotice, Nordstrom-4010-856-ShipNotice |
1 |
|
Functional acknowledgement |
Walmart-4010-997-FunctionalAcknowledgement, Nordstrom-4010-856-FunctionalAcknowledgement |
0 |
As per the B2B Manager subscription, overage is allowed for each EDI license component. The overage is applicable only in the production environment.
If a trading partner entitlement limit is exceeded, the flow associated with the oldest last run time will be disabled, similar to the platform flow disabling approach.
Example: Trading partner limit exceeded (3 trading partner entitlement)
|
Flow |
Trading partner |
Flow last run time |
Flow disabled? |
|---|---|---|---|
|
Flow-1 |
Trading partner-1 |
June 7, 2024 10:00 AM |
No |
|
Flow-2 |
Trading partner-2 |
June 4, 2024 10:30 AM |
No |
|
Flow-3 |
Trading partner-3 |
May 29, 2024 2:30 PM |
Yes |
|
Flow-4 |
Trading partner-4 |
June 4, 2024 8:00 PM |
No |
|
Flow-5 |
Trading partner-5 |
June 2, 2024 4:00 PM |
Yes |
Similarly, if the document type entitlement limit is exceeded, the oldest last run time flow for that document type will be disabled.
Example: Overage applied for the Basic tier (3 trading partners and 5 Doc types)
|
Flow |
Trading partner |
Doc type |
Flow last run time |
Flow disabled? |
|---|---|---|---|---|
|
Flow-1 |
Trading partner-1 |
Doc type-1 |
June 7, 2024 10:00 AM |
No |
|
Flow-2 |
Trading partner-2 |
Doc type-2 |
June 4, 2024 10:30 AM |
No |
|
Flow-3 |
Trading partner-3 |
Doc type-3 |
May 29, 2024 2:30 PM |
Yes |
|
Flow-4 |
Trading partner-4 |
Doc type-4 |
June 4, 2024 8:00 PM |
No |
|
Flow-5 |
Trading partner-5 |
Doc type-5 |
June 2, 2024 4:00 PM |
Yes |
|
Flow-6 |
Trading partner-1 |
Doc type-6 |
June 2, 2024 4:00 PM |
No |
|
Flow-7 |
Trading partner-2 |
Doc type-7 |
June 2, 2024 4:00 PM |
Yes |
-
If a trading partner is within entitlement limits but a document type exceeds limits, the flow is still disabled due to the document type overage.
-
If an overage is disabled, the system will not automatically re-enable flows. The user must manually enable the required flows.
-
This overage policy applies only to the new platform license type and is limited to production environments.
-
Sandbox and non-production environments do not support overage.
-
Overage does not apply to the existing endpoint license type, meaning the overage remains disabled in the current platform license type.