Modern Retail's CounterPoint integrator is a versatile and powerful tool, much like CounterPoint itself. Part of that versatility is your ability to customize the integrator to suit your needs, a concept that we care deeply about. In this article, we'll talk about "stored procedures", one of many avenues we can go down to customize your integration.
What Are Stored Procedures?
"Stored Procedures" are something that can be entered into the code for your integration. The technical realities of stored procedures are complicated, so we'll focus on the practical effects of some of their primary uses.
Stored procedures can be used either "post commit" or "pre commit", meaning they can take effect either before or after most major actions in CounterPoint. This includes things like an order being created, or an inventory change. Stored procedures can be used for both regular products and gridded products, although there is a distinction between the two in the code. Additionally, if you're using multiple locations, stored procedures will not function.
Because stored procedures are something coded into the integration, we recommend that only users with technical expertise attempt to create them. If there's something you want to do with stored procedures, we recommend either contacting us, or your CounterPoint dealer.
What Are Stored Procedures Used For?
Stored Procedures can be used for an incredibly wide variety of things, to the point where listing everything would be unproductive. Some of the more popular usages we've run into are sorting your catalogue into two webstores, or artificially "shorting" your inventory for a given product. There are also a set of default stored procedures in CounterPoint available for use.
If you're interested in setting up stored procedures for your integration, please feel free to contact us with a support request for further information.