A store-first plan
for Fronk Oil.

SHOP IMPLEMENTATION / OCTOBER 13, 2026

From catalog to online checkout

The shop preview uses the supplied Phillips 66 catalog for product search, category filtering, manufacturer documents, grade/package selection, a cart, and customer checkout review. No order or payment is sent. Existing customer-account payments and new storefront purchases are separate workflows. Fronk must approve the provider and accounting integration before the shop accepts payment.

What the source actually contains

The workbook contains 102 product rows, 227 grade/formulation records, and 429 provisional package codes. A missing 4T Mineral MA family is represented using its linked variant, package, resource, and thumbnail records, giving 103 displayed families. The recovered family has now been verified against the manufacturer, restored under Small Engine Oils > 4-Cycle (4T), and reconnected to its four existing historical package records for the demo. Eight original product families have no public material codes.

All package codes need current manufacturer and Fronk confirmation. Twenty-six package listings contain source conflicts, and the source has 32 package records without a matched grade/formulation; these groups can overlap. AAR 963 Oil now has a documented demo inference to the manufacturer’s single published grade, ISO 46, leaving 31 unmatched. A supplier listing identifies its code 1073906 as a 55-gallon drum. With the AAR grade correction and the restored 4T Mineral family, 374 source package records are selectable in the demo. Every one of the 103 product families and 227 grade/formulation options can enter the demo cart: 39 grades without a reliable package match use a clearly labeled “Packaging to be confirmed” selection. Those selections have no manufacturer material code or invented package size and are excluded from the inventory CSV. The AAR grade match is an inference because the historical package record omits the grade; 4T Mineral’s historical records explicitly state their grades. Current SKU/package approval remains required. This is a preview-selection check, not sale approval. All 429 records remain unapproved for live sales. Raw package notation and leading-zero material codes are preserved. The readable AAR package name has a linked supplier source; no Fronk internal SKU was invented.

No approved selling prices, currency, Fronk stock quantities, tax calculations, or shipping rates were supplied. Prices and totals are therefore shown as pending, never as free or zero. The payment control is disabled. Manufacturer thumbnails are taken directly from the supplied workbook; generic packaging is labeled illustrative. No AI-generated media is used. The HTML attachments contain fragments or correspondence, rather than product tables, and are excluded.

Build the production shop in Bitrix24

1. Start from one Bitrix24 Online Store as described in the store-first page map. Verify the account, plan, permissions, existing sales mode, template pages, and system assignments; preserve current customer and order records.
2. Approve the saleable assortment, exact manufacturer and Fronk item codes, grades, package units, retail prices/currency, stock rules, and document links. Resolve missing family and grade mappings before enabling purchases.
3. Use Bitrix24’s shared CRM/store catalog. The CSV import supports simple products without variants: the staging file provides one package/material-code row per simple product. For native grouped grade/package choices, create SKU properties and offers through the supported native interface or an approved API integration instead.
4. Create necessary product properties, download the account’s own import template, and map the staging columns. Keep material codes as text. The blank price/stock fields must remain unresolved until approved; importing the file is not sale approval. Reconcile external IDs with existing products and validate a small staging batch before a production import.
5. Use the retained native catalog, cart, checkout, and payment pages in that same Online Store. Add business pages within it, set business Home as Index page, and apply the shared Fronk header/footer. The custom demo cart is a reference and must be replaced by native store behavior.
6. Configure the approved payment provider, taxes, stock/reservation behavior, pickup/delivery eligibility, freight charges, fulfillment team, confirmation emails, and failed-payment/refund handling. Card details belong in the payment provider’s supported capture flow.
7. Test approved prices and quantities, out-of-stock products, tax/freight totals, successful/failed/cancelled payments, duplicate order prevention, CRM assignment, customer confirmation, and fulfillment receipt. Enable real purchases only after Fronk approves the results.

Catalog handoff

Download the 429-row staging CSV · Download mapping review records · Catalog corrections and evidence · Download the shop implementation guide · Manufacturer imagery source records

The CSV requires field mapping to the actual account template. It is not a native import of product variants, a price list, or a verified stock master. It contains no original correspondence or customer/payment data.

Official references: Native online store, catalog, cart, and checkout · CSV import and field mapping · Product variants · Website ordering and missing prices

What to demonstrate

1. Open the homepage and explore a service through the menu.
2. Choose an industry and follow its relevant services.
3. Open Request a Quote, enter sample details, and preview the request.
4. Use the top-right Customer Resources button. Choose Personal Credit, Business Credit, EFT, or Credit Card.
5. For a paper application, select Scan or Upload Completed Form in the Original Document panel. Try Sample Paper Form to show automatic extraction. Then show the customer reviewing and editing suggested answers beside the scan, selecting which answers to use, and confirming their accuracy. Unselected web-form values stay intact; the scan itself is not submitted.
6. Select Load Sample Details, then Fill & Review Application. Compare the filled PDF with the original blank form.
7. Download the filled application, then click Preview Department Routing to show the proposed handoff.
8. Resize to mobile to show the compact menu and stacked layouts.

Page blocks inside the Online Store

What needs account access

This is a Sites-hosted prototype, not an exported native Bitrix24 template. Its HTML and CSS are reusable references. Start from the Online Store template, add business pages inside that same store, and rebuild native content blocks or adapt permitted custom blocks after checking the account’s permissions and plan. Retain the template’s native catalog/cart/checkout roles and verify all system-page bindings. Exact font availability, editable block options, portal links, and CRM workflows remain to be verified.

The demo quote form validates entries locally and shows a request summary. It sends no email, creates no CRM record, and stores no details. Customer login links to the existing portal; no portal development is included.

Applications that move work forward

Customer Resources combines account access, applications, and reference tools at /resources/, reached by a single button at the top right. The previous /forms/ hub redirects there; individual application addresses remain available. The fixed header keeps navigation visible on desktop and mobile, and section links jump to the portal, applications, reference tools, or FAQs. Each of the four public applications has a matching web form. The demonstration fills the original PDF in the browser, preserves its printed terms, and offers a document preview and download. Signatures remain blank; documents are labeled unsigned demonstration copies.

Department labels are a proposal, not verified recipients. The routing button demonstrates the handoff but sends no email and creates no CRM record. No application details are saved by this prototype. Sensitive identifiers and payment credentials use fixed demonstration placeholders; do not enter real information.

Paper applications and customer review

Customers can keep using paper applications. In this prototype, each Original Document panel offers a completed-form import using a PDF, scanned image, or phone photo. The browser reads the information page locally and suggests answers only for editable fields. The customer sees the source scan, corrects missed or misread text, checks marked choices, selects the answers to use, and explicitly confirms accuracy before anything fills the web application. Existing values remain unless the customer selects their replacement. Customers can edit the web form again and review the filled PDF before the proposed handoff.

The sample-paper option generates and reads an actual sample document; it does not load canned extraction results. Files and unused extraction results stay in browser memory and are discarded when the import window closes. Selected answers remain in the open web form until the customer leaves or edits them. Source signatures and locked sensitive fields are never imported. The demo accepts up to three pages and 15 MB of sample or redacted PDFs, JPGs, PNGs, or WebP images. Recognition depends on an upright, closely cropped copy of the matching original form; skewed photos may need retaking.

The local reader works best on printed entries. Handwritten answers may be missed or misread and require customer correction. Production should evaluate a handwriting-capable document-recognition service against actual Fronk forms, with protected uploads, verified field mapping, customer review, and an agreed retention policy. Preserve the original signed application as a protected source record; importing text does not replace signatures or supporting documents.

Production form workflow

1. Confirm the department, responsible employee, and inbox for every application. Approve the original terms, required fields, permissions, and document templates.
2. Create native Bitrix24 CRM forms or a secure embedded form. Add completed-paper import with handwriting-capable recognition and mandatory customer review. Map every input to a CRM field and assign the submission to the agreed team.
3. Collect required permits and EFT supporting documents through authenticated, access-controlled uploads. Add the approved signature and consent workflow before an authorization is considered complete.
4. Generate the completed application using Bitrix24 document templates where available, or a secure server integration that fills the original PDFs. Verify the account plan supports the chosen automation; the browser demo is a reference implementation.
5. Automatically deliver the completed document or a protected document link to the relevant department, with CRM status, timestamps, and a failure/retry path. Use the mailbox and automation configured in Fronk’s account.
6. Run an end-to-end test for each form: validation, field mapping, document generation, signature/attachments, department assignment, delivery, and receipt. Launch only after recipients and Fronk approve the results.

Card entry must use a hosted payment-provider form and tokenization. Do not collect or email full card numbers or security codes through ordinary CRM fields. Bank details and personal identifiers need restricted access, protected transmission, and an agreed retention policy. Email notifications can point to a protected record rather than expose sensitive data in an attachment.

The fuel-tax link on the current site opens a Bitrix24 sign-in page. No tax application was invented. The hub retains that link and verified Texas and Oklahoma tax resources, plus the Hall Tank calculator. Add any specific approved tax application once Fronk supplies it.

Scope for the proposal

Include the Customer Resources page, four web forms, completed-paper uploads and handwriting recognition with customer correction/confirmation, PDF field mapping, approved signature and attachment handling, department routing, secure payment integration, and end-to-end testing as explicit implementation scope. Confirm Bitrix24 plan costs and any payment, signature, or integration service fees before quoting the production workflow.

Company and community pages

History, Meet Our Team and Koozie Fun are integrated as ordinary pages inside the same proposed Online Store. About opens their shared menu; the About overview and footer link to all three. The original /History/, /ourteam/ and /koozies/ paths are retained. History retains the original circular-photo and dark-date-badge timeline, its sixteen photo/story pairings, and a visible two-row archive carousel. June 12, 2027 remains an upcoming anniversary. The staff directory uses published names, roles and business emails. The gallery opens original customer photos with captions, previous/next controls and keyboard support.

These specific pages reuse genuine history, staff and customer photographs from Fronk’s source pages; generic business sections retain the stock imagery. No AI-generated media is added. Placeholder staff images are replaced by name initials, rather than assigning another person’s photo. Source URLs and asset records are included in the package. During the Bitrix24 rebuild, upload approved originals to native image/gallery blocks and resolve their returned URLs; adapt the optional gallery lightbox only where custom code is permitted.

Download company photo source records

Brand and content continuity

The original Fronk Oil logo is retained. Industry photographs use real Pexels stock photos; shop packaging imagery comes from the supplied manufacturer catalog. Current contact information, product availability, delivery area, and service descriptions should be confirmed before launch. No new testimonials or service guarantees have been added.

Stock photography credits

Original Pexels photographs depict industry applications; they do not depict Fronk Oil vehicles, facilities, or employees. Industry photography uses real stock photos; the shop uses supplied manufacturer imagery. No AI-generated media is included.

• Hero: Photo by Alexander
• Agriculture: Photo by Dariusz Grosa
• Fleets: Photo by Kelly
• Construction: Photo by Maarten van den Heuvel
• Industrial: Photo by Ali Mucci
• Repair: Photo by Artem Podrez

Pexels License · Download photo source records

Template package

The package includes the page markup, reference styling, demo interactions, store-first page map, and implementation guide. It is a starting point for adaptation, not a one-click Bitrix24 import.

Official implementation references

Bitrix24 CRM-form email automation
Bitrix24 CRM paperwork automation

Bitrix24 custom CSS documentation
Bitrix24 site and page settings