FRONK OIL SHOP — BITRIX24 IMPLEMENTATION HANDOFF
Prepared October 13, 2026

Intended sales flow: customers browse products, choose an exact grade/package,
review their cart and fulfillment details, and pay online through the approved
Bitrix24 payment integration.

FOUNDATION — ONE ONLINE STORE
Create or reuse one native Bitrix24 Online Store. Its template owns the catalog,
cart, checkout and payment flow. Add Fronk business/reference/application pages
inside that same store, select business Home as Index page, and link Shop to the
native catalog in the shared menu. Record and verify system-page assignments
separately; changing the Index page does not establish those bindings.
See ../bitrix-store-build-map.json for the complete page-role blueprint.

CURRENT PRESENTATION
/shop/                 Search/filter, product details and supplier documents
/shop/cart/            Package quantities, remove items and order summary
/shop/checkout/        Customer details, fulfillment preference and review

The present site is hosted with Sites. It is not a connected Bitrix24 store.
The cart contains only material codes and quantities in browser-tab session
storage. Contact/address inputs remain in the open page, are not persisted, and
are not sent. Checkout does not place orders, charge payments, collect card
information, calculate totals, reserve stock, or send email. Prices and totals
are shown as Pending. The final payment control is disabled.

SOURCE AND DATA REVIEW
Source: Phillips_66_Distributor_Catalog.xlsx
User attachment ID: file_000000004024820c8a2947d4b0c95a60
Supplier-catalog snapshot: October 7, 2026

102 original product rows; 227 grades/formulations; 429 package material codes.
4T Mineral MA is missing from Products but has linked variant, package and
resource rows. The preview restores this recovered family from its linked source records,
giving 103 displayed families. Current manufacturer data confirms the family,
category and all three grades; its restored parent now allows the four existing
exact historical grade/package associations into the demonstration cart.

All 429 package codes are provisional. The source supplies no approved Fronk
selling prices, currency, stock quantities, or internal item-code crosswalk.
Twenty-six package listings have source conflicts. The original source has 32
unmatched variants; one AAR 963 record is now inferred to ISO 46 for the demo,
leaving 31 unmatched. These groups can overlap. A total of 374 source package
records may enter the demo cart after the AAR correction and Mineral repair. This does
not approve any record for a live sale. Eight original families lack public
material codes. No missing identifier, unit, price or stock value was invented.

The 429 manufacturer identifiers are strings with leading zeros preserved.
Raw seven-digit source codes and raw package notation are kept separately.
Raw notation is preserved. The AAR 963 display label is 55-gallon drum (1/55),
corroborated by a supplier listing for code 1073906. Other package notation is
not expanded into guessed units. See catalog-corrections.json for the source
URLs and the single-grade inference; this does not approve a current Fronk SKU.

The source workbook's 38 actual manufacturer thumbnails are used locally.
Generic packaging and product-family imagery are illustrative; the pictured
grade or container may differ from the chosen package. Manufacturer/PDS/SDS
links retain their source URLs. No AI media is included.

The ATT*.htm files contain fragments, correspondence or signatures, not usable
product tables; they are excluded from the website and template package.
Original attachments are not included in the public package.

ALL-PRODUCT DEMONSTRATION
All 103 families and 227 grade/formulation options can enter the demo cart.
39 grades lack a reliable selectable package. They use a grade-only selection
labeled Packaging to be confirmed, with material code, package size, price and
stock unresolved. The cart/checkout show that status and allow review of the
shopping flow. Internal demo keys are never displayed as manufacturer codes.
They are not source package records and are excluded from the staging CSV.
The 429 original material-code records and their review flags are preserved.
Production must replace pending selections with approved, priced, stocked native
catalog products before allowing purchases. See catalog-review.json for gaps.

HANDOFF ASSETS
catalog.json                   Public storefront model and source row references
bitrix-catalog-staging.csv      429 package rows for account-specific mapping
catalog-review.json             Missing/conflicting mappings and review records
catalog-corrections.json        AAR grade mapping and verified Mineral-family restoration
image-sources.json             Manufacturer imagery provenance
images/                        Original embedded manufacturer thumbnails

The CSV is a staging mapping file, not the account's native import template,
an approved price list, a stock master, or a product-variant import. Its price,
currency and stock fields are blank. Approved for online sale is No on every
row. That approval column is informational and must not be mistaken for a
native Bitrix activation switch. Do not enable products for purchase merely
because this file has been imported.

BITRIX24 STORE-FIRST BUILD
1. Verify Fronk's account, subscription, permissions, existing catalog and
   sales mode. Inspect existing product IDs and customer/order records.
2. Reuse an appropriate native Online Store, or create one under Sites and
   Stores > Online Stores using a native store template. Record the store ID,
   page IDs, catalog section, shared areas and existing system-page assignments.
3. Create business Home, About, service/industry, Contact, Customer Resources
   and application pages inside that same store. Set Home as Index page and
   verify its mainpage role. Presentation Notes is demonstration material.
4. Retain the template's native catalog/product, cart, order checkout, payment
   and customer-area pages. Verify each applicable system-page assignment and
   resolve its actual native URL in the account; do not assume changing Home
   automatically repairs bindings. Preserve other template roles where used.
5. Configure one shared header/menu/footer. Logo/Home opens business Home;
   Shop opens the native catalog; all business and resource links use pages
   within this same store. Keep external customer/tax/tank tools intentional.
6. Resolve the source anomalies and approve Fronk's saleable assortment,
   internal/material codes, grade, package units, documents and imagery.
7. Supply approved retail prices/currency and stock/reservation rules, taxes,
   pickup eligibility, delivery geography, freight/rates and timing.
8. Choose the product model. Native CSV import supports simple products without
   variants: one verified package/material-code record per simple product can
   use the staging file. Grouped grade/package choices require native SKU
   properties and offers created manually or with the supported catalog API.
9. Create properties, download the account's actual CSV template and map fields.
   Keep material IDs as text. Reconcile external IDs with existing records and
   validate a small staging import. Review unmatched/conflicting data separately.
   Blank prices/stock remain unresolved; do not enable purchases from this draft.
10. Apply Fronk branding and scoped styles to native store/content blocks. The
    demo cart and checkout scripts are presentation references; production uses
    the template's native commerce behavior and supported payment capture.
11. Connect payment, fulfillment, tax/freight, CRM/team assignment, customer
    confirmations, failed/cancelled payments, refunds and stock release. Keep
    card details in the provider's supported payment capture flow.
12. Test root URL -> business Home -> Shop -> product -> native cart -> checkout
    and payment, cart continuity through business pages, customer area, approved
    price/stock/tax/freight rules, failures/duplicate prevention, CRM/fulfillment
    receipt, applications and department routing, and mobile/desktop navigation.
    Enable purchasing after Fronk approves the tested results.

TRANSFER AND TEMPLATE LIMIT
Documented native export/import transfers a whole native site or store between
Bitrix accounts. This build does not rely on merging a separate website and
store. The Fronk HTML ZIP is a reference package, not a native Bitrix export.
After a native transfer, reconnect account-specific CRM forms/widgets/apps and
verify domain attachment, catalog/system pages and integrations in the target.

FIELD MAPPING
External ID                  Candidate stable key P66-[material code]; reconcile
Name                         Family / grade / original package notation
Manufacturer                 Phillips 66
Manufacturer material code   Eight-digit text identifier
Raw source code              Original printed identifier, text
Grade / formulation          Exact supplier grade, subject to review
Package notation             Exact supplier notation; confirm unit definition
Section                      First supplied category path; others remain JSON
Description                  Supplied product-family description
Product image URL            Direct supplied manufacturer image URL
Manufacturer page            Official product page
Price / Currency / Stock     Blank pending approved commercial data
Approved for online sale     Informational No; map only if property is created
Verification status          Informational source review status
Matched variant ID           Reference join key, not a native offer import
Grade mapping basis          Explicit inference/evidence note where applicable
Package display label        Readable size with supplier corroboration
Package evidence URL         Source supporting the readable package name
Source sheet/row/evidence    Traceability properties

OFFICIAL REFERENCES CHECKED
https://helpdesk.bitrix24.com/open/25757867/  Start with a native Online Store
https://helpdesk.bitrix24.com/open/25558484/  Pages and shared navigation
https://helpdesk.bitrix24.com/open/21883080/  Index page setting
https://helpdesk.bitrix24.com/open/22630312/  Whole-site/store transfer
https://apidocs.bitrix24.com/api-reference/landing/page/special-pages/landing-syspage-get.html  System-page assignments
https://helpdesk.bitrix24.com/open/25809723/  Native catalog/cart/checkout overview
https://helpdesk.bitrix24.com/open/23513268/  CSV import and template field mapping
https://helpdesk.bitrix24.com/open/18839102/  Native product variants
https://helpdesk.bitrix24.com/open/17300484/  Ordering and absent Buy button
https://helpdesk.bitrix24.com/open/25826751/  Payment systems
https://helpdesk.bitrix24.com/open/17297482/  Delivery services
https://helpdesk.bitrix24.com/open/13727858/  Existing sales/order mode

ACCOUNT VALIDATION REMAINING
No Bitrix24 account or payment connection was available for this work. Store
entitlements, processor availability, custom-code support, import mapping,
orders, CRM, stock, emails and fulfillment have not been tested in Fronk's
account. The current demo requires a native Bitrix build/integration to go live.
