You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
QBO allows a "bundle" of products to be defined as a single product. For example: a) core membership; b) training manual; etc. Adding that single "bundle" has the effect of adding the list of sub-products to an invoice.
For EOSC, this allows them to use a simple invoice from WA and turn it into a complex invoice inside QBO.
From a technical QBO perspective, specifying a "bundle" item (via Make.com / API) requires a slightly different approach than a standard product/item.
Several possible approaches:
Make.com logic that searches each product first to determine the type of product and then adjusting the invoice creation appropriately. CON: this approach increases the operations count for every invoice.
Additional configuration settings to define if the QBO product is a bundle item or standard item. MAke.com scenario uses this setting to adjust the invoice creation logic. CON: changes to config data structure and mapping guide.
The text was updated successfully, but these errors were encountered:
Request from EOSC - Drew Robinson.
QBO allows a "bundle" of products to be defined as a single product. For example: a) core membership; b) training manual; etc. Adding that single "bundle" has the effect of adding the list of sub-products to an invoice.
For EOSC, this allows them to use a simple invoice from WA and turn it into a complex invoice inside QBO.
From a technical QBO perspective, specifying a "bundle" item (via Make.com / API) requires a slightly different approach than a standard product/item.
Several possible approaches:
The text was updated successfully, but these errors were encountered: