VayuDocumentationIntegrationsAPI ReferenceChange Log
SupportGet started now
GuidesProducts

Linking a Catalog Product

Link fixed or service products to catalog products and understand inherited values.

Linking a Catalog Product

You can link a fixed or service product to an existing catalog product to reuse its configuration.

When you select a catalog product, Vayu:

  • Uses the catalog product name and stores a reference to the linked product.
  • Copies the description, if the catalog product has one.
  • Copies the Disable description setting.
  • Copies configured credit types.
  • Copies available integration mappings, including NetSuite, Anrok, Stripe Tax, QuickBooks, Xero, and Paddle.

Inherited Tax Settings

Anrok and Stripe Tax settings can be inherited from the linked catalog product.

Vayu resolves these settings in the following order:

  1. Product- or contract-level override
  2. Linked catalog product setting
  3. No value

A product- or contract-level setting always takes precedence over the catalog setting.

If you clear an override, Vayu falls back to the value configured on the linked catalog product. The UI displays this as Inherited from catalog.

How Linked Values Are Applied

Not all values inherited from the catalog behave the same way.

Anrok and Stripe Tax settings are resolved dynamically. If the corresponding setting changes on the linked catalog product, the inherited value reflects that change unless an override is configured.

Other values, including the description, credit types, and most ERP and integration mappings, are copied when the catalog product is linked. These should be treated as initial values rather than continuously synchronized settings.

If you select a different catalog product, Vayu clears the values copied from the previous product before applying values from the newly selected product.

If you switch to a custom, unlinked product, Vayu removes the catalog reference and clears values copied from the catalog, including the description, credit types, and integration mappings.

Empty catalog descriptions and empty integration mappings are not copied.

Usage Products

Usage products handle catalog linkage differently.

For usage products, the catalog relationship is managed through the associated meter. The meter provides the relevant integration mappings and credit types rather than inheriting the full fixed or service product configuration described above.

On this page