DigittrixBack to agriculture services

From field record to available stock.

Explore a small agriculture workflow: record a harvest, keep a draft during simulated network loss, then synchronize and dispatch produce.

Interactive prototype · fictional sample records

Demo connection available. Synchronization writes to a second ledger in this browser.

Drafts are saved locally so you can reload this page and continue.

01 / Field capture

Record a harvest

Two fictional crop records are available. A new entry stays pending until you synchronize it.

Enter 0.01–10,000 kg. Each saved entry gets a unique operation ID.

02 / Local queue

Harvest records 0 pending

Retrying synchronization reuses the same operation IDs, so accepted records are not counted twice.

    Retry sends the same sample records to the simulated ledger again. Check that received stock stays unchanged.

    03 / Inventory

    Reconcile a produce batch

    Received
    0 kg
    Dispatched
    0 kg
    Available
    0 kg

    Dispatch is blocked in simulated offline mode or when the requested quantity exceeds available stock. No delivery is booked.

    04 / Traceability

    Demo activity log

    Follow the record IDs and batch movements created in this browser.

      Try it yourself

      Four checks you can reproduce

      1. Enable simulated offline mode, save 120 kg against P-07, then reload. The draft should still be pending when local storage is available.
      2. Disable offline mode and synchronize. B-104 should show 120 kg received.
      3. Retry the last sync three times. Received stock should stay at 120 kg.
      4. Dispatch 80 kg. Available stock should become 40 kg. Trying to dispatch another 50 kg should be rejected.
      What a production pilot still needs

      This prototype does not implement a server, authentication, multi-user conflict resolution, backups, a service worker or physical devices. A production pilot needs server-side permissions and validation, transactional stock updates, device and network tests, storage recovery, version conflict handling and field-user acceptance testing.

      Built by Digittrix as an original sample workflow. The checks describe this prototype’s behavior, not measured business outcomes or agronomic advice.