Upgrade From Legacy Versions

Older Product Fees versions may use a different setup model than current versions.

If You Are Upgrading

During upgrade, migration logic may convert legacy fee data and settings into the current format used by the extension.

Legacy Setup Indicators

If your store used an older setup, you may still see legacy fee-related product attributes or old fee labels in historical data.

After Upgrade

• Runtime fee calculation uses the current Product Fees data model.
• Existing sales documents keep historical values for reporting consistency.

Migration Did Not Recreate Expected Fee Setup

Common reasons:

• legacy source data is incomplete
• legacy prefixes/settings were not available
• products had no effective fee values

If this happens:

1. Recreate fee types in Admin
2. Reassign fees to target products/websites
3. Re-test cart, checkout, order, invoice, and credit memo flows

See:

• Create Fee Types
• Assign Fees To Products