So I'm trying to figure out the best structure for this scenario:
We have products, which we manufacture and sell.
We sell these products at multiple price points (distributor, wholesale, retail, and custom price points for certain customers).
I'm trying to figure out how I could have multiple price sheets, linked somehow with products.
Realistically, we can get away with price sheets being a separate table and not linked in with anything, but I feel like that makes adding it to the DB redundant.
If it could be linked, the idea would be that when quoting or "invoicing"* we could select the price sheet which would then populate the cost based on the product we select.
I thought I almost figured it out but then it fizzled into a pile of 'not going to work'.
*we do our actual invoicing in an accounting software, but setting up pseudo-invoicing would be beneficial as it could act as a packing slip as well as an invoice displaying our product by the pack or carton instead of individual unit.
Hi Julian
That's what I had a vague idea of in my head. Good to know I'm on the right track.
I'll update this thread with my results to benefit anyone else wanting to do the same.
I am having to check if all of what we want to do can be done with netsuite though, as we are hoping to have it implemented to allow for an account system that can be used globally.
edited to amend
Looking at netsuite, it may suite our needs, but there's a chance it wont be approved so going forward I'm going to go ahead with Ninox as both an on-boarding process and contingency plan in case net suite doesn't happen for a while.
Hi Sarah
I'm glad that you're enjoying Ninox - I'm a great fan! And I saw that Sakshi from Ninox has responded to you - I would take her up on her offer - and maybe start to attend some of their webinars.
Re your data structure, I think I would probably do this with a table linked to Products and a Price List table (say called the third table Product Prices) so that you could hold multiple prices (by type - e.g. retail, wholesale etc) for each product. You could even set up a price list for particular customers. From a UI point of view, you could either enter prices via a Price List page or via the Product page (or both).
Then, when selecting a product for an Order Line, you could use the Ninox Language to look up the correct value for that type of customer (you could hold which price list to use for the customer on their record).
Hope this helps.