FRONK OIL WEBSITE CONCEPT — JESSE BY DESIGN

This is an interactive reference site, not a native Bitrix24 template export.

STORE-FIRST PAGE MODEL — OCTOBER 13, 2026
Target: one Bitrix24 Online Store containing the business website and shopping
pages. Business Home is the Index page. Shop is one shared menu item and opens
the native catalog within that same store.

The prototype has 29 routes: 22 customer-facing production page references,
Presentation Notes, its BookWorks workflow demonstration, the customer invoice
preview, and the legacy /forms/ redirect. Customer-facing pages include Home,
About, the service/industry overviews and detail pages, Contact/Quote, Customer
Resources, four applications, Shop, Cart and Checkout. Presentation Notes and
the proposal banner are demonstration material, not production store pages.
See bitrix-store-build-map.json for the full route-to-native-role blueprint.
Native store/page IDs and URLs remain unset until account configuration.

BITRIX24 STORE-FIRST BUILD
1. Verify the account, plan, permissions and existing store/catalog records.
2. Reuse an appropriate Online Store or create one under Sites and Stores >
   Online Stores from a native template. Record store/page IDs, shared areas,
   catalog section and template system-page assignments before changes.
3. Add Fronk's business/reference/application pages inside that same store.
   Set the business Home as Index page and verify the mainpage role separately.
4. Retain the native catalog, basket, order checkout and payment pages. Keep
   their system assignments, customer-area role and native product flow valid.
   Resolve actual native URLs in the account; do not deploy the demo cart as
   production commerce or create a separate website/store merge workflow.
5. Apply shared menu/footer blocks, colors and fonts. Shop links to the native
   catalog; logo/Home links to business Home. Adapt CSS to actual block IDs.
6. Map approved catalog data and configure pricing, stock, payments, taxes,
   pickup/delivery, CRM assignment and confirmations. Connect CRM forms and
   custom application integrations within that same Fronk account.
7. Verify Home/Shop/product/cart/checkout, cart continuity across business
   pages, customer tools, forms/routing, legacy URLs and mobile/desktop access.

Native Bitrix export/import transfers whole native sites/stores between
accounts. This static HTML ZIP is a reference package, not that native export
and not a way to merge a separately created website with a storefront.

HTML sections and CSS are references, not guaranteed native-editable blocks.
Custom HTML/JS, fonts, and CSS availability must be checked in the real account.
This prototype requires no framework, backend, database, or custom API.
The four application forms fill original PDFs in the browser, preview and download
unsigned demo copies, and demonstrate proposed department routing. No details
are sent to Bitrix24, stored, or emailed. Sensitive fields are fixed placeholders.
The /resources/ hub includes the customer portal, four applications, original
PDFs, tax references, the tank calculator, and FAQs. /forms/ redirects there;
/forms/<type>/ applications retain their addresses. One Customer Resources
button appears in the fixed header. Its measured height reserves page space;
the mobile menu scrolls within the viewport and anchor jumps clear the header.
See forms-assets/sources.json for original document provenance and
forms-assets/applications.json for editable field-to-PDF mappings.
PAPER APPLICATION IMPORT
Each Original Document panel accepts a completed sample/redacted PDF or up to
three page photos (JPG/PNG/WebP), 15 MB total. PDF.js 5.6.205 and Tesseract.js 7.0.0
are vendored locally with workers, English data, and licenses. Scans stay in
browser memory, never reach a server, and clear when the import window closes.
Selected reviewed answers remain in the open web form until leaving or editing.
Known-template regions isolate editable answer fields; source titles are checked.
The customer reviews/edits every selected answer and confirms accuracy before
applying it to the web form. Existing unselected values and locked sensitive
fields remain unchanged. Checkbox choices require manual customer confirmation.
Printed entries work best; handwriting needs correction. Production must evaluate
a handwriting-capable recognizer with protected uploads and source-record retention.
See forms-assets/import-regions.json for top-left Letter-page OCR regions.

Production requires native CRM forms or a secure integration, document generation,
approved signatures, protected attachments, verified recipients and department
rules, payment-provider tokenization, and end-to-end delivery testing.
Do not collect or email live card numbers or CVV through ordinary CRM fields.
External links open existing Fronk customer tools. These are not rebuilt.
The original Fronk Oil logo is retained. Industry photos use real Pexels stock
photographs; shop thumbnails use supplied manufacturer images. See
photo-sources.json and shop-assets/image-sources.json for provenance.
No AI-generated media is permitted in this project.
Fonts use Google Fonts with system fallbacks.

Official references:
https://helpdesk.bitrix24.com/open/8745423/
https://helpdesk.bitrix24.com/open/21883080/
https://helpdesk.bitrix24.com/open/25757867/
https://helpdesk.bitrix24.com/open/25558484/
https://helpdesk.bitrix24.com/open/22630312/

Form workflow references:
https://helpdesk.bitrix24.com/open/25885167/
https://helpdesk.bitrix24.com/open/24369266/

COMPATIBILITY AUDIT — OCTOBER 7, 2026
Confirmed reusable asset formats: six industry JPEGs, original JPEG logo,
four original PDF downloads, and the added PNG favicon. Font/layout/header
code must be adapted and scoped to native blocks; current CSS is global.
Native CRM form design uses supported Design controls; arbitrary CSS/JS
form styling is not supported. Reviewed values can use the documented
CRM form setValues API after field mapping. Native file upload does not
establish OCR. Scan extraction/customer review and exact original-PDF
overlay generation remain custom integrations requiring resource-hosting,
worker/module/WebAssembly/security-policy and account-plan validation.
Native document templates must be DOCX, <=2 MB, with CRM field codes.
The importer supports matching Fronk PDF/JPG/PNG/WebP applications, not
DOC/DOCX or arbitrary resume/document extraction. Live department routing,
email/document delivery, secure payment capture and signatures are not
connected in this demonstration. Fronk’s account has not been tested.
See /implementation/#bitrix-compatibility for source-backed audit details.


SHOP DATA AND CHECKOUT PREVIEW — OCTOBER 13, 2026
The Shop, Cart and Checkout Preview use the supplied Phillips 66 catalog and
real embedded manufacturer thumbnails. No orders/payments are sent. Prices and
stock are unknown, and every package code remains unapproved for live sales.
See shop-assets/bitrix-shop-handoff.txt and the Presentation Notes shop section
for source anomalies, CSV mapping and native Bitrix24 deployment prerequisites.
Original HTML correspondence and unrelated attachments are excluded.

AAR 963 DEMO MAPPING CORRECTION — OCTOBER 13, 2026
The historical code 1073906 / display code 01073906 is linked to the sole
published ISO 46 grade for demonstration, with the inference recorded. Its
readable 55-gallon drum label is corroborated by a direct supplier listing.
Original source grade/code/notation remain preserved; prices, stock and current
SKU approval remain unresolved. See shop-assets/catalog-corrections.json.

ALL-PRODUCT DEMO — OCTOBER 13, 2026
All 103 products, 227 source grades/formulations and all 429 source part
numbers can enter the demo cart and checkout. Source records with unmatched
grades have clearly labeled provisional choices; raw approval flags remain
unchanged. The 4T Mineral parent is restored using manufacturer evidence.
39 grades lacking a reliable package use Packaging to be confirmed selections,
with no manufacturer code, package size, price or stock fabricated. These
grade-only demo selections are excluded from the 429-row source inventory CSV.

BOOKWORKS CONNECTOR PRESENTATION — OCTOBER 13, 2026
Fronk reports BookWorks Accounting 4.5.152.0 and a Bitrix24 subscription with
storefront and websites. The reported module/version does not verify API
access, Warehouse & Lubes or MobileConnect licenses, or any connector operation.
Paid BookWorks support is off limits; use existing internal records first.
Basey's online customer-account payments and Tiger Payment Solutions in-store
payments are existing flows, not proof of a new storefront payment integration.

Open /implementation/#bookworks-workflow, then the interactive demonstration
at /implementation/bookworks/. It is an illustrative staff screen, not the
actual BookWorks application, and is outside the customer-facing menu/checkout.
All connector actions run locally against fictional customer/stock records.
The complete inventory view contains all 429 source package records plus 39
grade-only pending-package demo records; new example fixtures are separate.
Columns are a proposed BookWorks-style adapter layout, not a verified vendor
API schema or production import format. Opening stock is 100 sample units per
record; unit/warehouse/item mappings require confirmation. Checkout places a
browser-local demo order automatically. All source and pending choices use
fictional item mappings automatically. Open order qty updates immediately;
simulated on-hand changes at shipment. Older saved inventory gains missing
catalog records and resumes checkout orders held only for mapping, preserving
existing orders, item IDs, balances, invoices and manual interruption progress.
Reservation simulation is OFF by
default and can be enabled as an optional assumption for a proposed capability.
Staff shipments reduce simulated on-hand stock and, when enabled, reservations;
they do not create an invoice or receivable. Customer status updates locally.
No Bitrix or
BookWorks API is connected; no orders, billing entries or payments are sent.
The current demo cart can be copied read-only for a presentation; only products
and quantities are read, and the customer/address are always fictional.
Orders and inventory persist in localStorage in this browser until Clear demo
data is used. Tabs on the same origin share live updates; different browsers,
devices and origins do not share this ledger. Presentation cart copying leaves
the cart unchanged; Place demo order clears the submitted cart. Sample stocks and BookWorks IDs are fictional, and all
commercial prices remain pending. This is not a production queue or ledger.

To illustrate reservations, enable the optional assumption before sending the
10-case example. This does not verify reservation support in BookWorks.
Then Simulate transfer -> enter 6 and click Simulate shipment
-> Sync preview -> Simulate remaining shipment
-> Sync preview -> Create sample invoice preview -> Simulate payment record
-> Sync preview.
With that assumption enabled, simulated inventory follows
100/0/100 -> 100/10/90 -> 94/4/90 -> 90/0/90.
Use Simulate interruption before Simulate transfer, then Retry simulation to demonstrate
a lost acknowledgement after one local proposed order record without a duplicate order.
Replay a processed event to show no repeated local stock or document effect. Cancel
remaining releases only undelivered reservations after partial shipment.
Leave the optional reservation assumption off to demonstrate the default scope.
Review demo-only SKU matching for grade-only selections and real-unit mapping.

Production requires a separate secured background service with a durable queue
and action ledger. Fronk's Bitrix order mode is unknown. New accounts use CRM
Deals; legacy Deals + Orders remains for existing users. Any sale.shipment.*
write route requires a verified account mode and actual underlying order.
crm.item.delivery.* is read-only and cannot perform shipment updates.

Confirm the actual BookWorks 4.5.152.0 API contract, licensed modules,
unit/customer/location mappings, reservation support, and inventory/AR posting
ownership. Public sample fuel endpoints do not prove packaged-oil support or
that shipping posts AR in Fronk's installation. Native Bitrix reservations can
exceed available stock; an authoritative concurrent-stock check is required.
Invoices/payments must use the confirmed billing operations. Payment-record
updates do not charge a card; provider capture/refunds need separate support.
BookWorks' public CardPointe/MobileConnect offering does not verify Basey's,
Tiger or Fronk's module access.

Bitrix online events do not retry automatically. Durable connector retries,
periodic reconciliation and tested recovery are required. Duplicate protection
also depends on verified remote lookup and uniqueness/idempotency semantics;
local action IDs alone do not guarantee exactly one remote write. Evaluate
offline events only against the account's supported permissions and plan. See
bookworks-connector-handoff.txt and the demonstration readiness notes.

CUSTOMER INVOICE DEMONSTRATION — OCTOBER 13, 2026
Fill items in the proposed staff workflow, then Create sample invoice preview. The
invoice covers newly filled quantities only; later fills create a separate
invoice. Earlier invoice amounts/quantities remain unchanged. Replaying an
event or clicking again cannot bill the same quantity twice in the local model.
Invoice creation is a separate simulated document action and never moves stock.
This is not proof of a BookWorks billing operation or invoice API.

Staff can Preview sample customer invoice, Print / Save as PDF, download a portable
HTML copy, or Preview invoice email. The customer checkout confirmation gains
an invoice link after synchronization; the invoice page uses acknowledged
customer records unless explicitly opened as a staff preview. With automatic
staff updates off, use Sync preview before the customer can see a new invoice.
Email previews remain local and send no message. Every recipient and customer
is fictional; customer checkout contact details remain unstored.

Every invoice line uses a fixed FICTIONAL $100.00 per selected package/item to
demonstrate integer-cent totals. Actual catalog price fields remain unknown.
Tax and delivery are NOT calculated, not set to zero or assumed exempt. The
example goods total excludes those charges. Documents say DEMONSTRATION
INVOICE — NO PAYMENT DUE, including printed and downloaded copies.
Payment marks the issued sample invoices only; no funds or credentials move.
The document is generated locally, not retrieved as a BookWorks PDF. Bitrix24
supports native invoice generation and email with the required configuration
and a connected mailbox, but Fronk's setup and cross-system transfer are untested.

The /shop/invoice/ route is a presentation document preview, not a deployed
production billing page or verified native Bitrix invoice template. Production
requires the approved invoice owner/numbering, rates, taxes, freight, terms,
partial billing and credit policy, protected customer access, secure document
generation/delivery and verified customer email assignment. Send a protected
link or approved attachment through Fronk's configured system and track
delivery/failure separately from generating the invoice.

COMPANY AND COMMUNITY PAGES — OCTOBER 13, 2026
The original /History/, /ourteam/ and /koozies/ addresses are retained.
All three appear under About in the shared desktop/mobile menu, on the About
overview, and in the footer. Add them as ordinary pages within the same
Bitrix24 Online Store; the updated page map has 29 routes and 25 production
page references. The three presentation routes and forms redirect stay separate.

History preserves the original page’s sixteen photo/story rows, circular
portraits, dark date badges, red headings and fine timeline. The thirteen-photo
archive is a visible two-row carousel with pagination and full-size viewing.
All 29 genuine source images remain included. June 12, 2027 is explicitly upcoming. The team page retains 22 published
staff names, departments, roles and business emails. It uses 18 source-associated
photos and initials where the source has a placeholder; no stock actor stands
in for a named employee. Koozie Fun includes all 19 current source gallery photos
and captions, with a full-size photo viewer supporting keyboard navigation.
Original photos are local assets, not embedded dependencies on Fronk's CDN.
Generic marketing photography remains the previously recorded stock collection.
No AI-generated media was used. See company-assets/provenance.json and
company-assets/content.json for source-page/image URLs and asset records.

Rebuild the timeline, directory and gallery with native Bitrix image/text/gallery
blocks. Upload approved originals and replace URLs with Bitrix's returned URLs.
The custom lightbox is a reference enhancement; adapt it only where the account
allows the required custom code. Ordinary image links work without JavaScript.
Confirm current staff details and photo publication rights during production
content review; no new CRM or accounting integration is introduced.
