INVIZ.tv / Reporting sources / System 04 of 04
2023Recorded work
Shopify order collection for creator reporting
Test whether store orders are available before designing how to separate creators’ sales in the reports.
- Noah’s contribution
- Set up the demonstrated store connection, tested order retrieval and briefed the remaining store/data-structure work.
- Historical stage
- Narrated successful order-fetch test for one store; broader source mapping and rollout pending.
- Part of the business
- INVIZ.tv overview ↗
- Shopify
- Shopify API
- Make
- Google Sheets planning
Inside this system
The workflow
The handoffs
inside the work.
Follow the main path and its branches. Select a step for context; the account below explains what was built, tested or planned.
- One-store app connection
Configure the demonstrated store-specific connection and order access. - Scheduled native-module retrieval
Choose the retrieval start and run the Make order-fetch test. - Retrieved Shopify order data
The narrated test returned orders for the connected store. - Vendor association option
Investigate whether the vendor field can distinguish the creator. - Product/collection association option
Investigate product or collection data and required access for creator matching. - Unresolved creator-data model
Select the final association rule and reporting-table structure. - Other-store connection work
Extend source connections after the one-store component test.
Key records
The information
that carries forward.
| Record | Information | Purpose |
|---|---|---|
| Store connection | A store-specific app/connection and order access for the tested store. | Establish a usable source before building the report. |
| Retrieved orders | Order data returned by the narrated Make test. | Check that the source connection can supply reporting inputs. |
| Creator association design | Potential vendor or product/collection relationship, still under investigation. | Avoid mixing creator sales when a store serves multiple relationships. |
Inside the system / 01
Prove the source connection before designing the full dashboard
INVIZ’s merchandise reporting required access to commerce data as well as accounting uploads. The Shopify walkthrough focused on the source-collection component: Noah had added a custom app for one store and used a native Make module to test whether it returned orders.
The demonstrated module was scheduled rather than a webhook. Noah explained the difference between the selected recent window and changing where the retrieval should start, then narrated a successful execution. This established a concrete component-level result: the tested store connection could return order data. It did not establish that every independent store was connected or that historical imports were complete.
Inside the system / 02
Resolve how a shared store maps to creators
The next design question was separating sales when one store contained merchandise for several creators. Noah looked for collection information in the returned data and considered whether the vendor field could provide the association instead. Product data and its permissions were another possible route.
These were active design questions in the walkthrough. The source fetch worked, but the final creator-separation rule was not demonstrated. The requested reporting table also remained to be designed. Revenue, sales and product measures were discussed as potential dashboard inputs; their appearance in a planning conversation does not prove completed metrics or a reconciled reporting model.
The walkthrough used native modules first to validate the connection, leaving more granular API or GraphQL requests as options if filtering required them. That order of work kept the initial question narrow: can this store provide the required source records? More complex aggregation and display logic depended on resolving the data and ownership questions afterward.
Inside the system / 03
Keep iteration visible as the scope changes
Noah asked a teammate to extend connections to the other stores and work on the data structure. A separate connection-swapping walkthrough described changing Google Sheets connections across a scenario and questioned which stores needed explicit filters. It also disconnected the item-level portion because top-product tracking was outside the immediate scope.
The tested result was order access for one store. A finished multi-store reporting structure, complete creator separation and a completed reporting rollout were not established.
Within INVIZ.tv