Episerver Commerce Data Enrichment Cheat Sheet
We all know the feeling, having to setup tax jurisdictions, warehouses, payment methods or shipping methods can be a tedious exercise, which quickly can be interfered by human mistakes if it isn’t applied consistently. Not everyone is aware that these data aspects easily can be scripted, hence automatically moved across databases used by folks within your development team and to the more stable environments such as Integration, Pre-Production and Production.
When would these scripts be exeucted?
We tend to rely on Episerver’s Initialization mechanism to apply these data enrichment scripts.
You though need to remember that these Initialization Modules are re-executed every time instances of your application starts up, hence it will always be your responsibility to ensure the same data record is not added over and over again. Please also note the ModuleDependency annotation, which forces these to be initialized after the Episerver Commerce engine has been setup.
Let’s have a look at some data enrichment scenarios.
Tax Groups, Tax Jurisdictions, Tax Categories and Taxes