Protect account settings
Store the Locally API key in encrypted tenant settings and record the account identifiers required by the approved implementation.
Local inventory / Configuration-led integration
Connect CMS Max Product Discovery to Locally
Help shoppers move from product research to nearby availability through a governed product-locator implementation.
CMS Max includes encrypted Locally credential settings, report and split identifiers, product-name formatting, and product-page widget configuration fields. The current repository does not contain a completed Locally API connector or registered frontend bootstrapper, so feed exchange, identifier retrieval, widget rendering, and transaction behavior must be verified or implemented for each production scope.
- Encrypted API-key setting
- Report and split configuration
- Product-name mapping fields
- Production runtime validation
Online to offlineProduct-to-local-availability path
Implementation review
Local inventoryLocally + CMS MaxConfiguration-led integration
Catalog ownerCMS Max
Local networkLocally
Widget fieldsConfigured
RuntimeValidate
01Product is publishedCMS Max maintains customer-facing content
02Identifiers are matchedCatalog and Locally records must agree
03Shopper checks nearbyApproved locator experience is invoked
04Availability is shownProvider data and retailer feeds determine results
What the integration does
Build local availability on top of trustworthy product identity.
The native administrative surface captures an API key, report ID, split ID, product-name format, display toggle, company ID, and base address. Current evidence supports configuration readiness, not an unconditional claim that CMS Max automatically exports inventory, retrieves a real split ID, renders every widget, or synchronizes local transactions.
Align product identity
Define how CMS Max brand and product names, UPC or EAN identifiers, variants, availability, price, and retailer records correspond to Locally.
Plan the product locator
Use the product-page display fields as the implementation contract for an approved Locally widget, fallback, analytics, and customer journey.
Operating boundary
Separate configuration fields from the live data and widget runtime.
Local inventory is credible only when catalog identity, retailer feeds, account settings, frontend behavior, and customer expectations are verified together.
| Area | Primary owner | Supported contract |
|---|---|---|
| CMS Max product content | CMS Max | Owns the website product page, catalog content, brand presentation, SEO, navigation, and conversion context. |
| Local inventory network and tools | Locally | Operates provider locators, retailer connections, inventory data, account products, and available online-to-offline services. |
| Credential and identifier settings | CMS Max tenant | Stores the API key, report ID, split ID, product-name format, widget toggle, company ID, and base address. |
| Feed and product matching | Joint implementation | Requires agreed identifiers, source fields, frequency, validation, rejected-record handling, and ownership. |
| Widget or transaction runtime | Scoped delivery | Must be implemented or verified in the installed CMS Max release; it is not proven by the settings page alone. |
Connected workflow
Start with account readiness and a product-match proof.
Do not scale to every SKU and location until a representative set proves the identifiers, inventory freshness, widget behavior, and ownership model.
Discover
Confirm the Locally program, merchant or brand role, account access, retailer network, available products, IDs, feed requirements, widget option, transactions, and support.
Map
Document CMS Max product, brand, UPC or EAN, variant, price, availability, location, and media fields against the provider contract.
Configure
Enter the secured API key and verified identifiers manually, define product-name formatting, and prepare the company and base-address settings for the approved widget.
Prove
Validate a small product and location set through feed processing, matching, nearby results, out-of-stock states, mobile use, accessibility, analytics, and fallback behavior.
Operate
Monitor feed freshness, rejected items, unmatched identifiers, retailer coverage, product-page rendering, provider changes, and customer outcomes.
High-value applications
Connect online product research to nearby purchase options.
Available Locally programs vary by account and agreement; CMS Max should publish only the options that are contracted and accepted.
Product locator
Help shoppers identify nearby retailers associated with a product from the CMS Max product journey.
Local availability context
Present provider-supplied availability with clear freshness, distance, location, and fallback expectations.
Brand-to-retailer discovery
Support manufacturers that want product pages to route qualified demand to participating local dealers.
Retail catalog participation
Prepare CMS Max product identity and retailer data for an agreed Locally inventory or marketplace program.
Governance and trust
Protect credentials and prevent stale availability promises.
A local-availability claim can send a shopper to the wrong store. Security, identifier quality, feed freshness, and disclosure deserve production controls.
Credential handling
Keep the Locally API key encrypted and out of page source, analytics, logs, screenshots, repositories, and public support artifacts.
Manual identifier verification
The current Get Split ID action is not backed by a completed provider call; obtain and verify production identifiers through the approved account process.
Catalog identity
Use stable UPC or EAN and variant conventions where required, and review duplicates, bundles, discontinued items, and brand-name changes.
Availability clarity
Define data freshness, out-of-stock behavior, distance logic, retailer status, provider outages, fallback contact paths, and correction ownership.
Search and conversion continuity
Keep the CMS Max product page authoritative and locally useful.
A locator can improve conversion, but search authority still depends on crawlable CMS Max product, brand, category, dealer, and location content that remains useful without the provider widget.
Canonical product pages
Maintain durable CMS Max URLs, unique copy, specifications, media, structured data, availability context, and internal links for every indexable product.
Dealer and location content
Publish accurate local destinations with addresses, hours, services, brands, contact paths, and meaningful geographic context.
Crawlable fallback
Explain where-to-buy options in HTML and keep a store or contact path available when the locator cannot load.
Measured local intent
Track locator opens, searches, retailer views, outbound actions, and accepted conversion signals without treating widget impressions as sales.
Implementation sequence
Prove matching, freshness, and customer behavior before scale.
The launch plan should treat the provider account, inventory sources, catalog IDs, CMS Max page, and customer-facing locator as one system.
Contract
Confirm the Locally products, commercial agreement, data fields, retailer role, feed route, widget or API rights, transactions, support, privacy, and success measures.
Prepare
Clean catalog identifiers, document product and location ownership, enter verified settings, and implement the approved data and frontend runtime.
Accept
Test matched and unmatched SKUs, variants, prices, inventory age, locations, distances, empty results, mobile, keyboard use, analytics, privacy, and outages.
Release
Expand in controlled groups and monitor rejected records, stale data, missing retailers, widget errors, customer reports, and provider updates.
Implementation references
Review the platform and provider evidence.
Provider products and requirements change. These references support discovery; the production implementation and acceptance evidence remain authoritative for each CMS Max site.
Locally FAQ
Questions teams ask before they connect.
Final scope depends on account configuration, customer journeys, data policy, connected systems, operational ownership, and acceptance criteria.
Does CMS Max include Locally settings?
Yes. CMS Max includes encrypted API-key storage plus report ID, split ID, product-name format, product-page display toggle, company ID, and base-address settings.
Does saving those settings automatically connect the full Locally runtime?
No. The current repository does not show a completed provider API connector or registered frontend bootstrapper. Feed exchange, identifier retrieval, widget rendering, and transaction behavior must be implemented or verified for the production scope.
Can CMS Max automatically retrieve the Split ID?
Do not rely on that today. The inspected administrative action contains a placeholder rather than a completed Locally API call, so production IDs should be obtained and verified through the approved account process.
What product identifiers should be prepared?
Confirm the exact Locally program requirements. Stable UPC or EAN values, brand, product name, variant identity, availability, price, location, and retailer mappings commonly matter, but the contracted provider schema is authoritative.
Can a Locally locator appear on CMS Max product pages?
CMS Max includes fields intended to configure a product-page widget. The actual installed frontend rendering, provider code, styling, privacy, analytics, accessibility, and fallback must be accepted before launch.
Who owns local inventory accuracy?
The retailer inventory source, Locally processing, catalog matching, and CMS Max presentation all contribute. The implementation plan must name owners for feed freshness, rejected items, product identity, retailer status, and customer corrections.
Connect with confidence
Build a credible bridge from product discovery to local availability.
Bring the Locally agreement and account, merchant or brand role, catalog schema, UPC or EAN coverage, retailer network, locations, feed method, widget requirements, privacy rules, analytics plan, sample products, and support owners. CMS Max will define the implementation and acceptance contract.
Locally is a trademark of its respective owner. CMS Max scope is described on this page and may differ from the provider's complete product offering.
Building Relationships with Web Developers and Marketing Agencies that want better results
The world's fastest and most SEO friendly website code.