vault backup: 2024-09-27 10:15:49

BigCommerce.md

@@ -0,0 +1,4 @@
+e-commerce solution Logos has included as part of its replatform.
+
+Website: https://www.bigcommerce.com/
+Developer documentation: https://developer.bigcommerce.com/

Daily Notes/2024/09/2024-09-26 (Thursday).md

@@ -1,3 +1,18 @@
 # Work
 
 # Meetings
+## Kyle K. 1:1
+Kyle explained some of the history of the product and SKU integration to [[BigCommerce]]. Currently, the integration does this:
+- Products are integrated as products with a SKU pattern of "LP-*product ID*"
+- SKUs are integrated as products with the SKU set to their SKU ID from Products API
+- Products are related to SKUs in a product modifier picklist.
+This is not a very ideal structure because [[BigCommerce]] provides the product-variant structure which would match out product-SKU structure well.  In addition, product modifiers are things that usually have a price-tag associated (like monogramming a tote bag or something)--this is not how we are using them. 
+
+A couple of reasons we went this route:
+1. [[BigCommerce]] doesn't allow a mix of physical and digital products as variants of the same product.
+2. We wanted a single PDP for products that have physical and digital products.
+3. We didn't split up products with physical and digital SKUs because, at the time, [[BigCommerce]] APIs did support searching products by the fields (assuming we'd relate the physical and digital products should a custom field or related products data) we would have needed to search by to provide a unified PDP.
+4. Variants may have also had odd tax implications--Kyle couldn't remember exactly.
+5. The product modifier picklists were used, though we essentially use them as a way to display the format options (which SKU you want to buy) instead of how [[BigCommerce]] expects modifiers to work.
+
+I'd much rather see us structure the data accurately and work around the issues of two PDPs and tax problems. I'm afraid we're going to run into trouble later because of the way we've structure BC.