NOGL / Connections
Plan your connections
Start with the decision you need to make, then agree the sources, permissions and delivery scope. A platform name is a conversation starter; confirm availability for your account before planning a rollout.
Commerce and public sources
Check public sources · private setup is separate
Shopify · Salesforce Commerce Cloud · BigCommerce · Adobe Commerce / Magento · WooCommerce · Oracle Commerce
A supported public catalog scan examines information visible on a public store. It is different from connecting a customer-authorised commerce account for private catalog, order or inventory data. Tell us the store domain, country and category first; source access and coverage must be checked for that market.
Public search signal
Put a read-only public signal next to your own sales. Choose one term, one region and one time window. The signal shows relative search interest, not sales.
Example series: one term, one region, one time window
- Term
- Wool coat (fictional term)
- Region
- Region 1 (fictional)
- Time window
- Last twelve weeks (fictional)
| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Relative interest (0 to 100) | 34 | 36 | 35 | 41 | 40 | 44 | 47 | 46 | 52 | 55 | 58 | 61 |
Direction: rising, from 34 in week 1 to 61 in week 12.
The signal needs no account. It forecasts no demand and changes no plan. Values are illustrative until an authorised public source is agreed for your market.
All values are fictional and illustrative. Relative search interest is not a sales figure, and this card changes no plan.
For an account connection, confirm platform version, access permissions, data fields and refresh needs with NOGL. A public scan does not grant private account access or establish an order-sync connection.
Review product information before the handoffOperations, reporting and promotion
Pilot scope and setup to confirm
Oracle NetSuite · Taboola · MNTN · reporting and team tools
Define the operational question and the report or handoff your team needs. Inventory, finance and advertising workflows can require private records and approval from the responsible system owner.
A KPI moved outside its expected range (fictional)
The operator sees the KPI, its expected range and the day its value left that range. A flagged point on the trend line marks a change to check, not a finding.
- Expected range
- 94–98 %
- Flagged value
- 81 %
Likely cause, in one sentence Draft explanation, not a finding
Shipping success fell from 96 to 81 per cent, which matches a carrier's collection pause in one region.
Business impact in the first 10 minutes
312 orders affected. No customer data is read.
- Process step with the change: Payment confirmation: 81 exceptions in the window (fictional).
The example is fictional. The explanation stays a draft until a person accepts it, and nothing is detected from your data on this page.
Ask which connection and read/write scope can be qualified for your workspace. Confirm credentials, delivery destination and a reviewed test plan before rollout. Automatic purchase orders or advertising writeback are not promised by this page.
One product record, reviewed before handoff
Attributes and assets for a product sit in one record. A person reviews the record and sets its status before anything leaves the workspace.
Fictional example: one product with three attributes and three linked assets.
Sample wool coat, size M (fictional)
- Article number (SKU)
- EX-SKU-301
- Record status: Draft, Complete or Archived
- Draft
Attributes
- Colour: navy
- Material: wool
- Size: M
Linked assets
- Front photoLinked
- Care labelLinked
- Size chartLinked
Assets are linked to the product and are not copied into it.
Review step, as text: a person checks the attributes and assets, then sets the record to Complete.
This section shows the layout with a fictional product. It stores nothing, reads no catalogue data and sends nothing to a channel.
Regional performance view (sample)
A sample of how store sales and assortment gaps could be read by region once a store list and a sales source are agreed.
- < 65
- 65–79
- ≥ 80
- Assortment gap (sample)
Regions and values are fictional. They show the layout only and are not your data or a customer result.
Customer data and service
Pilot scope and setup to confirm
Fairing · KnoCommerce · Okendo · Gorgias
Reviews, survey responses and support records have different access and privacy requirements. Public review evidence is different from a private customer or support-system connection.
Before sharing records, agree the necessary fields, authorised users, processing terms, retention and deletion requirements. Confirm the connection's current status for your use case; do not send customer exports or access tokens in a general enquiry.
Support insight, shown with fictional data
A support lead sees why customers write in: return reasons, size-fit complaints and product defects, grouped by product. The team sees the same insight beside the ticket in the helpdesk it already uses.
- Return reasons9
- Size-fit complaints14
- Product defect escalation3Escalated to a named product owner. A person decides the next step.
Notice when a category rises above a threshold you set
Helpdesk view (fictional sample)
EX-TICKET-01 · EX-PRODUCT-07
The panel is fictional. It reads no customer data and sends nothing to your helpdesk.
Call-centre analytics
Pilot scope and setup to confirm
Call transcripts · sentiment · coaching notes · CRM sync status
Call recordings can show topics, customer sentiment and coaching points for each team member. The analysis is only as good as the recording source, the consent rules and the review step, so each source is agreed before rollout.
Agree the contact-centre platform, the recording export or webhook, the CRM objects that receive notes and who approves any coaching change. Confirm recording consent and retention for your market.
| Call (fictional) | Transcript excerpt | Sentiment | Coaching note for review | CRM sync status |
|---|---|---|---|---|
| EX-CALL-01 | Customer asked whether the wool coat in size M runs small. | Neutral | Offer the size guide before quoting a delivery date. | Not synced in this example |
| EX-CALL-02 | No transcript for this call | Negative | Check the delivery promise wording with a team lead. | Not synced in this example |
| EX-CALL-03 | Recording consent not confirmed: no analysis shown | Not synced in this example | ||
Live recordings, speech processing and CRM write-back are not connected in this example. Coaching notes are suggestions for a human reviewer.
A connection for your workflow
Pilot scope and setup to confirm
Custom data sources and destinations
Describe the decision, source system and desired handoff. We can discuss a bounded pilot with a named owner, clear data scope and acceptance criteria rather than assume every system is already connected.
Agree feasibility, responsibilities, access and success criteria before implementation. A useful qualification includes an authorised test account, observed data flow, failure handling and human review of the result.
Return by region and channel
See the return estimate for each channel in each region as a band, not as a single number. Fixture values only; nothing is recommended or applied.
Example grid: three regions, three channels
| Channel | |||
|---|---|---|---|
| Region | Online store | Marketplace | Retail partner |
| Region 1 | 12 %Return band: 9–15 % | 8 %Return band: 5–11 % | 10 %Return band: 7–13 % |
| Region 2 | 11 %Return band: 8–14 % | 14 %Return band: 6–24 %Wide band: estimate weak | 9 %Return band: 6–12 % |
| Region 3 | 7 %Return band: 4–10 % | 13 %Return band: 9–16 % | 6 %Return band: 3–9 % |
A wide band means the estimate is weak. The bands show model uncertainty, not a forecast. This view changes no budget.
Budget scenarios for these channels are compared on the marketing mix modeling page. Open the budget scenarios
All values are fictional and illustrative. The grid changes no budget and recommends no plan.
Design review references
Pilot scope and setup to confirm
Figma · FigJam
A reference frame shows a design beside a review decision, so reviewers can check the source without leaving the board. It is a viewer, not an approval: the decision stays with the named reviewer.
Confirm which file, page and frame may be shown, who can see it, and whether viewers may pan, zoom or change pages before the reference goes on a board. A link that needs an organisation login is shown as such.
Reference frame (fixture, not a customer file)
Shared by linkViewer controls set for this reference
- Pan and zoom
- off
- Page selection
- off
- Full screen
- on
A reference is not an approval. Record the decision in the review itself.
Trade and tariff reference
Public reference, not a duty decision
U.S. Harmonized Tariff Schedule: public search and revision archive
A public tariff-line record shows the code, its description, the General and Special duty columns, the unit of quantity and the schedule revision it was read from. It is a reference for the planning conversation, not a classification or duty decision for a shipment.
Check the product description, origin, destination and any preference claim with your customs adviser before relying on a rate. Public records do not show customs entries, binding rulings issued to your business or private filing history.
Open the USITC reference record
Social content and shoppable listings
Pilot scope and setup to confirm
Short video · LIVE showcase · product listing · stock status
Social content can lead a buyer to a product page. A listing is only useful if the product, price and stock shown match the catalogue, so each link needs a source and a refresh time.
Agree the store and channel, the catalogue fields to sync and who owns the stock rules, and how often stock is refreshed. Confirm the connection status for your account before a live session.
Shoppable listing (fictional)
EX-PRODUCT-201
Products in this live session (fictional)
Live stock reservation, price feeds and order sync are not part of this example.