DESIGN PROPOSAL Prepared by Jesse by Design Presentation notes
Family owned and operated since 1947800-722-3835
Customer Resources
Back to Presentation Notes

BOOKWORKS INTEGRATION CONCEPT / PRESENTATION ONLY

Explore a proposed staff workflow.

A browser-local simulation for discussing a possible handoff between Bitrix24 and BookWorks. It is not an official BookWorks interface or proof that Accounting 4.5.152.0 exposes these API operations.

Browser-local concept only.Orders, stock, reservations, invoices, email previews, and sample payments use fictional local records. Fronk’s API access and supported operations are unverified. No real order, stock movement, billing record, email, or payment is created.

CAPABILITY VERIFICATION / PRESENTATION ONLY

What is documented, and what still needs proof.

Fronk reports BookWorks Accounting, version 4.5.152.0. That identifies the installed application; it does not verify API access, licensed warehouse or delivery modules, or the operations shown below. This is a simulation for discussion, not proof of the installed API.

Proposed functionPublic documentationFronk installation status
Orders, products, prices and stockBitrix24 documents Deals versus legacy Deals + Orders and catalog and stock APIs. BookWorks advertises platform APIs with sample endpoints; its Warehouse & Lubes offering is separate evidence from the Accounting module name.Not verified end to end. Confirm store mode, API entitlement, module access, item/package units, prices and supported order operations.
Reservations and availabilityBitrix24 deal reservations can exceed available stock. BookWorks warehouse materials show committed stock, without establishing a reservation/release API for this version.Assumption only. BookWorks reservation operations and stock ownership are unknown. Reservations alone do not guarantee prevention of overselling.
Partial shipments and cancellationsBitrix24 supports partial shipments through sale APIs with administrator access. crm.item.delivery.* is read-only. BookWorks advertises delivery integration.Not verified end to end. Confirm BookWorks partial fills, remainder cancellation, return updates, and the permitted Bitrix24 write route.
Customer invoices, PDF and emailBitrix24 documents invoice PDF generation and email through a connected mailbox. This does not prove BookWorks invoice API operations.Bitrix24 feature documented; configuration untested. BookWorks invoice generation/retrieval, delivery, stock posting and accounts-receivable ownership remain unverified.
Payments and refundsBookWorks advertises MobileConnect with CardPointe payments. That does not establish compatibility with Fronk's reported Basey's online-account payments or Tiger in-store processing.Not verified. No processor migration, new storefront checkout, refund integration or BookWorks payment posting is promised.
Automatic updates, recovery and duplicatesBitrix24 online events are not retried after a failure. Recovery, durable queues and duplicate protection require connector engineering and testing.Concept behavior only. BookWorks notifications, lookup and retry semantics are unknown; browser event replay does not verify a production connector.

Verification scope. Paid BookWorks support is off limits for this phase. Use existing authorized company records to establish licenses, API documentation, permissions and configuration; leave missing evidence unknown. No installation-level API test has been completed. No real system is connected.

LOCAL ORDER FEED

Watch demo orders arrive.

Local updates within this browser. Open checkout in another tab on this same domain; its fictional demo orders appear here automatically. No Bitrix24 or BookWorks API is connected.

Open Shop in another tab

Placed demo orders will appear here. You can also start the example below.

This feed stores product codes and quantities with fictional customers in this browser. It does not store customer checkout details. Clear demo data removes the local demonstration records.

CHOOSE A MANUAL SCENARIO

A ten-case order, step by step.

The example begins with 100 illustrative units of stock. Imported demo-cart items use fictional customer and inventory records.

Preparing the sample workflow…

FULL DEMONSTRATION INVENTORY

A stock view for the whole catalog.

429 source material-code records plus 39 grade-only demo records. All demo choices have fictional local item mappings; live approval is still pending. Item IDs and all stock counts are fictional. Generic inventory fields are used here; the actual BookWorks import and API schemas are unverified.

Preparing the full inventory table…

Loading inventory…

Each record opens with 100 fictional stock units at Booker Demo Location. Placed orders increase Open order qty. Simulated shipments reduce open quantities and sample on-hand stock. Reservations change only when their optional assumption is enabled. Saved demo inventory gains missing catalog records without clearing existing orders or balances. The CSV is demonstration data, not a production import.

01 / LOCAL SHOP RECORD

Website order preview

Sample order details will appear here.

Optional assumption, off for new examples. Choose before transferring. BookWorks reservation support and stock ownership are unverified; reservations alone do not guarantee prevention of overselling.

02 / LOCAL HANDOFF SIMULATION

Connector concept

The handoff queue will appear here.

Illustrates intended retry behavior on local records. Production recovery, unique references and duplicate protection require supported operations and controlled tests. The browser has no system credentials.

03 / PROPOSED OPERATIONS

Proposed staff workflow

The fictional staff order will appear after handoff.

Select an order to see how many items remain on each line.

Choose an order line for a simulated shipment. Simulate cancellation cancels every unfilled line in this local record and releases any assumed reservation. Real BookWorks operations are unverified.

ILLUSTRATIVE INVENTORY

Physical stock, reservations, and availability.

The 100-unit opening balance is fictional, including when actual catalog descriptions are used.

Inventory cards will appear here.

SHIPMENT HISTORY

Simulated stock movements.

Sample shipments and cancellations will appear here.

BILLING ILLUSTRATION

Sample invoice and payment.

Fictional invoice and payment references will appear here.

Create a sample invoice preview after simulated filling. Fictional $100-per-package pricing illustrates totals; no payment is due and email previews send nothing. Invoice timing, stock posting and accounts-receivable ownership are unverified for production.

ITEM MAPPING

A shared item reference for each line.

Manufacturer material codes are source references. BookWorks item IDs are fictional and need a verified crosswalk.

The sample mapping will appear here.

EVENT JOURNAL

Follow the handoff and every update.

This journal belongs to the browser demonstration. A production connector needs protected durable records and reconciliation.

Sample events will appear here.

BEFORE PRODUCTION

Evidence needed before an integration commitment.

BookWorks access and records

Use authorized internal records to confirm API availability, licensed modules, item/customer IDs, supported writes, stock rules and invoice ownership. BookWorks Accounting 4.5.152.0 alone does not verify these operations.

Reported accounting tools and existing customer-account or in-store payment flows do not verify this connector or a new storefront payment processor. None is connected or migrated by this demonstration. Paid vendor support is outside this phase; API and workflow questions remain for later authorized verification.

An external connector

Use an asynchronous, secured connector with server-side credentials, a durable queue, duplicate protection, retries, and reconciliation. No secrets belong in browser code.

Bitrix24 online events are not retried after failure. Implement and test durable recovery and reconciliation. Confirm the store's Deals or legacy Deals + Orders mode and use a permitted shipment write route; crm.item.delivery.* is read-only.

Complete a controlled test

Agree on approved item mappings, prices, stock, reservations, partial shipments, cancellation, invoice ownership, and payment reconciliation. Test failures, retries, repeated events, and department receipt before launch.

Importing the demo cart reads its product codes and quantities only. It keeps the customer fictional and does not change or submit the customer’s cart.

Source documents for the proposed workflow

Bitrix24 sale eventsBitrix24 event deliveryKey Infotech software services

Download connector implementation notes

Back to Presentation Notes

LET’S GET TO WORK

What keeps you moving?

Contact Sales