Case study · Not documented
Culture Goods
The commercial logic lived in a spreadsheet; the customer experience lived in Shopify. We connected the two.
- Shopify
- Google Sheets API
- JavaScript
- Custom app/integration
- Discipline
- Dynamic pricing · Google Sheets integration · Shopify automation
- Year
- Not documented
- Engagement
- Fixed scope
- Status
- Live

01Context
- Connect Google Sheets data to Shopify.
- Build dynamic product/pricing calculations.
- Keep non-technical business inputs manageable outside source code.
Culture Goods needed pricing or product calculations driven by structured data maintained outside Shopify.
Google Sheets provided a familiar operational interface for managing the source data, but the storefront needed reliable programmatic access to those values.
HeapByte built a custom integration connecting business-managed spreadsheet data with Shopify calculation logic.
02What was in the way
- 01
External source of truth
Shopify could not assume the relevant calculation data lived permanently in product records.
- 02
Data consistency
Spreadsheet edits and storefront requests need predictable field mapping and validation.
- 03
User-facing performance
External data dependencies cannot make product interactions feel slow or unreliable.
03Architecture
What we built, and what we deliberately left alone.
- 01
Sheets integration
Structured spreadsheet data is retrieved programmatically.
- 02
Calculation layer
Business formulas run independently of visual storefront components.
- 03
Shopify presentation
Calculated results are surfaced within the ecommerce experience.
Delivery
- Data structure review
- Google Sheets integration
- Calculation engine
- Shopify implementation
- QA
04Outcome
- Business data
- Externally manageable
- Calculation
- Dynamic
- Manual code edits
- Reduced
Pricing inputs editable through Google Sheets
Shopify responds to structured source data
Operational changes do not always require development
05Engineering notes
- Sheets API
- Structured worksheet ranges are consumed programmatically rather than scraped.
- Field mapping
- Spreadsheet columns map explicitly into calculation inputs.
- Dynamic calculation
- Customer-facing values are derived from current business-managed data.
- Separation of concerns
- The merchant controls source values while application code owns formulas and validation.
What we took from it
- 01Familiar business tools can remain useful when connected through a clean API layer.
- 02Spreadsheet integrations need strict schemas even when the UI feels informal.
- 03Calculation logic should be isolated from network and UI code.
- 04External data should be cached or validated where appropriate.
Disciplines applied
Next case study
Forged 4x4
We developed Shopify Plus checkout-extension functionality for custom calculations and business rules that needed to operate inside the purchase experience.
Similar problem?
We will tell you whether this approach fits.
Every store is different. Send us yours and we will say what we would actually do — including when the answer is less work, not more.