BloxLoop questions, answered

BloxLoop Business Suite is a connected business-software platform from BloxLoop Systems. It combines focused apps for purchasing, inventory, customer relationships, sales, distribution, finance, reporting and customer access on one shared BloxLoop Core. A business can begin with the workflow it needs and connect more suites under explicit entitlements and governed handoffs.

BloxLoop is designed around clear record ownership, one verified identity, tenant-scoped access, incremental adoption and configurable workflows. Connected suites exchange controlled handoffs instead of silently editing one another's records, which helps preserve accountability from supplier through customer.

BloxLoop Core is the shared foundation for identity, tenancy, security and platform contracts. A suite is a customer-facing business app with its own records and permissions. A module is a capability inside a suite. An Industry Solution configures approved suites and terminology for a field without creating a competing platform or source of truth.

No. Enterprise is an edition and deployment model over the same BloxLoop Core and suite code. It is assessed for organization-specific governance, integrations, infrastructure, security, capacity and implementation rather than maintained as a customer-specific fork.

Yes. Each suite has its own membership and entitlement checks, so activation can be phased. Connected workflows are enabled only after the relevant tenant links, record-owner contracts and permissions are verified. Buying or creating an account for one product does not silently unlock every suite.

No. Public information may describe a current app, a request-based activation path, a controlled industry plan, an assessed Enterprise option or a later roadmap item. A page, feature description, migration or test is not proof that a tenant is activated. Your approved entitlement and activation record control what your organization can use.

Purchasing supports supplier sourcing, requisitions, independent approvals, RFQs, quote comparison, versioned purchase orders and expected-delivery evidence. It hands approved procurement outcomes to other suites but does not post stock into Inventory.

Inventory manages product and location records, receiving, stock balances, movement history, reservations, transfers, counts, adjustments, traceability and returns according to the activated plan. It is the authoritative owner of stock truth.

CRM manages accounts, contacts, leads, opportunities, proposals, customer-success work, support cases and governed follow-up. It can hand an accepted commercial outcome to Sales without becoming the owner of orders, deliveries or finance records.

Sales manages customer and service catalogs, dated pricebooks, controlled orders, fulfillment requests, commercial records and governed commissions. It does not directly mutate inventory, complete delivery or move money.

Distribution manages manual dispatch planning, drivers and vehicles, loading, manifests, delivery attempts, private proof of delivery, exceptions and return handoffs. It owns delivery execution evidence while Sales and Inventory retain their own records.

Finance manages controlled customer invoices, receivables, supplier payables, payment evidence, allocations, statements, adjustments and commissions. Submitted payment evidence requires authorized review; it is not automatic payment confirmation or money movement.

Reports & Analytics provides governed metrics, dashboards, reports, private exports and scheduled reporting from approved source contracts. It reads from accountable suites without becoming a competing operational system of record.

The Portal gives prospects and customers one verified place for inquiries and for records or actions that a provider explicitly shares. It shows limited projections and accepts governed requests; it does not expose the full staff workspace or create a second source of truth.

A source suite publishes a versioned handoff or approved projection. The receiving suite records its own response, status or downstream record without overwriting the source. Tenant links, permissions, idempotency and audit evidence are checked at the service and database boundaries.

The current public Plans directory provides verified comparisons for BloxLoop Inventory and BloxLoop Clinic. Other Business Apps use assisted activation unless a product-specific comparison is published later. Enterprise remains assessment-led.

Inventory Free is one nonrenewable, $0 workspace for 60 active days using the approved base Standard workflow within strict published limits. It requires an eligible verified account, no card and no automatic paid conversion. The plan page is authoritative for current capacity and lifecycle details.

Standard is for growing operations that need the ready-to-use multi-location Inventory core, structured purchasing and receiving, transfers, customer fulfillment, controlled adjustments and core reporting. Activation is assisted, and the plan page shows current regional prices, capacity and optional guided setup.

Business adds deeper traceability, lots, serials, expiry controls, bins, stronger approvals and permissions, richer reporting and assisted implementation. Current capacity, add-ons, implementation terms and regional prices must be read from the authoritative Inventory comparison.

Inventory Enterprise is for assessed requirements such as organization-specific workflows, dedicated infrastructure, advanced governance, integrations, custom security policies, migration and managed implementation. Scope, price, schedule and service commitments are proposal- and contract-defined.

No. Starter remains a historical compatibility edition and is not a current new-sale plan. New customers should compare Free, Standard, Business and Enterprise on the current Inventory plan page.

The published Clinic guide describes Free for 60 days, Standard, Business and assessed Enterprise. Clinic Free is for fictional evaluation and configuration. A public plan or paid activation does not by itself authorize real-patient production use; privacy, security, environment and acceptance gates are verified separately.

No. Inventory prices and limits belong to Inventory. Other suites remain assisted-activation offerings unless their own verified public comparison says otherwise. A proposal must identify the products, capacities, implementation and recurring charges that actually apply.

Use the product-specific Plans page immediately before deciding. Published regional amounts are product-specific list prices rather than currency conversions. Tax treatment, implementation fees, billing interval and final activation terms are confirmed in the applicable comparison and proposal; this FAQ intentionally does not duplicate changeable prices.

No. Identity proves who is signing in; it is not the same as suite membership, tenant selection, role, plan or entitlement. Every protected suite independently checks the active organization, membership, permissions and assurance level before allowing data access or an action.

Enter the same email address used for the request. BloxLoop sends a short-lived, single-use code. Use only the newest code and never share it with BloxLoop staff or anyone else. Successful low-risk portal verification may create a limited AAL1 session; protected data and actions still require the policy's stronger checks.

Check the email address and spam folder, allow for delivery delay, then request one new code and use only that latest code before it expires. Avoid requesting several codes in quick succession because older codes become invalid and rate limits may apply. If the error continues, contact support with the approximate time, page and a masked email address—never send the code itself.

AAL1 is a limited assurance level permitted only for explicitly enabled low-risk prospect or portal engagement. AAL2 is required for protected operational data and sensitive actions, using an approved second factor or equivalent policy. BloxLoop enforces the boundary on the server, database and storage layers; hiding a button is never the security control.

Private records carry explicit tenant context and are protected by membership, entitlement, role and database row-level policies. Services reject missing or mismatched tenant context, and public hosts must not expose tenant records. Dedicated Enterprise infrastructure can be assessed when contractual requirements call for it.

Yes, within the activated product and plan. Roles, capabilities, location scope, approval rules and maker-checker controls are enforced at protected boundaries. Governed changes and sensitive actions retain audit evidence according to the suite and contracted retention policy.

No. Public pages may show product explanations, fictional interface previews and plan information, but they must not disclose a tenant's catalog, customers, suppliers, stock, documents, financial records or operational history. Private records require the correct host, session, tenant and authorization checks.

Start with the BloxLoop Privacy Notice. Product lifecycle and retention rules appear in the applicable plan or agreement. Backup, recovery, data location, dedicated infrastructure and custom retention requirements are confirmed during Enterprise assessment when they differ from the shared service policy.

Read the Privacy Notice →

No. The published Free paths do not automatically convert or charge a card. Continue only through explicit paid activation. Review the product plan page for active, read-only, recoverable-deactivation and deletion-eligibility milestones before relying on a Free workspace.

Not generally. Current paid BloxLoop activation is assessment- or request-led unless a product page explicitly says otherwise. A submitted payment receipt is evidence for authorized review, not automatic confirmation, and BloxLoop does not claim connected money movement where it is not verified.

BloxLoop verifies the requester and organization, clarifies the workflow, products, users, locations, data, controls and integrations, then documents the applicable plan or proposal. Paid access, implementation and production use begin only after scope, authority and activation are explicitly confirmed.

No. Free is self-guided. Inventory Standard offers the current published optional setup path, Inventory Business has a required implementation package, and Enterprise implementation is assessed. Other products follow their own proposal or published plan terms.

No. Internal suite contracts support approved BloxLoop handoffs, while external client APIs, webhooks, third-party systems, scopes, quotas, network controls and service commitments require explicit activation or an assessed Enterprise scope. A product page must say when an external API is included.

Use the Customer Portal to submit a new inquiry or open the request and support history that has been explicitly shared with you. Include the affected product, organization, approximate time, page, expected result and safe screenshots. Do not include passwords, one-time codes, secret keys, card data or unnecessary personal records.

Submit an inquiry →

Describe the business outcome and control requirements in an assessment. BloxLoop may satisfy the need through existing configuration, an entitled add-on, an industry pack, an integration or a proposed roadmap item. A request, demonstration or target date is not a production commitment until it is approved, implemented, accepted and activated.