Handcrafted pages will produce the best engagement. I created a system in 1995 that allows you to make the webpage the way you want it and have the cart or the database fill in the blanks. I recently modernized the system using newer compilers for longevity, I use markers for the content that is to be inserted. These markers follow the format of ##(variablename)## and #*RepeatBlock*#. For example, In a single product view the would be no need to repeat anything. But in a multi-product list or subtotal listing items in the cart we repeat data "for each". So, the rule of thumb is to ask yourself is there possibly more than one of something. Like a table with tr tags seperating each row.

Further, the variablename in the cart variables are static or unchanging while those of a database would be up to the database field being accessed. For example, ##ItemID## in the cart is refering to an item in the cart or about to be in the cart. Of course, adding items to the cart will follow normal GET/POST variable declaration. I am refering to output. The subtotal is a page that uses the output from the shopping cart so it will use ##ItemID##.

If a page absolutely must be database driven. The fieldname is the name used. ##FieldName## usually enclose in code that also has #**#. Cases where a database might be used is where there are too many products to realistically design pages for each. I am not really in favor of websites that need this approach but Amazon has lots of products to offer so it would be used in some scenarios.

It goes without saying again that I have been in this industry a long time an have seen all these providers pop-up with their canned solutions. I can say this, it will likely not end well if your business relies on the same thing everyone else is doing. It is my brandcrafting that will. Of course, I am biased. But I would tell a relative the same thing a thanksgiving. This is not a sales tactic. Whatever you decide, thanks for at least looking at my solution, I wish you success in your business.