Software built around your operation.
BulkTally builds software for bulk material yards and transportation operations. From inventory and bills of lading to custom operational workflows, each implementation is scoped around the work your team needs to do.
Start with the work you need to do.
Explore our yard product or talk through a custom transportation system. Each engagement has its own scope, implementation plan, and ongoing service agreement.
BulkTally Yard
Storage inventory and bills of lading in one private system. Track silos, tanks, bins, and stockpiles, finalize load tickets, and give customers access to their own records.
Explore BulkTally YardA TMS shaped around your operation.
Work with us to define a transportation management system around your team's workflows, data, and reporting needs. Custom TMS implementations are scoped and quoted separately from BulkTally Yard.
Explore custom TMSSilo to BOL, without the spreadsheet.
Built around one invariant: on-hand equals baseline plus finalized net weights. Drafts never touch storage. Finalize posts the lines and locks the ticket.
Live storage inventory
Silos, tanks, bins, or stockpiles, named in your language. Levels, capacity, LOW alerts, calibrated baselines.
Draft → finalize BOLs
Inbound and outbound weight lines, live tally, truck tare/gross, then a green finalize that commits inventory and locks the ticket.
Straight bill PDFs
Printable bills of lading with your letterhead, ready for the scale house and the customer file.
Customer portal
Customers see only their company. Server-enforced scope on every query. Never trust the UI alone.
Roles that match the yard
Developer, admin, supervisor, staff, customer. Daily ops stay fast; deletes and calibration stay gated.
Your instance, your terms
White-label product name, company, container vocabulary, units (lb / ton / gal / bu), and ticket prefix: config, not a fork.
Full audit history
Every ticket create, edit, finalize, storage calibration, and user change is logged with who did it and when. Calibrations record old value to new value with a required reason. Administrators review it all under Admin > Activity.
Reports & exports
Shipping volume over time, customer mix, per-product and per-location rollups, and CSV export on every report card. Custom reports are quoted up front.
A day at the scale house.
Four steps from empty ticket to locked BOL and updated on-hand.
Create the BOL
Customer, destination, carrier, product. Direction: loading out or receiving in.
Add weight lines
Net weights per storage unit. Live tally shows what inventory will look like after finalize.
Finalize
Green commit. Lines post to storage, ticket locks, acting user is logged.
Print & report
Straight bill PDF for the truck. Daily log and reports for the office.
The screens your crew will live in.
Every shot below is from the live demos, not a mockup: storage that reconciles, BOLs that finalize cleanly, and one product speaking each industry’s language.
Draft freely. Finalize when it’s real.
Weight lines and a live tally before anything hits storage. Green Finalize posts the ticket and locks it.
- OUT · Loading / IN · Receiving
- Live tally projects on-hand after finalize
- Drafts never touch totals or reports
The day’s tickets, at a glance.
Net movement, open drafts, and per-product rollups, built for the scale house and the office in the same view.
- Signed inbound / outbound amounts
- Draft vs finalized, clearly marked
- Filters that match how crews actually search
The weekly numbers, already added up.
Shipping curves, who took what, and how the mix breaks down by product and by location, without exporting to Excel first.
- Shipping volume over time
- Customer mix at a glance
- Per-product and per-location rollups
- CSV export on every report card
- Same numbers the tickets already proved
Need another view of your data? Custom reports are scoped and quoted up front, with delivery timing agreed before work begins.
No more end-of-day load out report!
Customers sign in and see their loads the moment your scale house finalizes them, so nobody compiles a daily LOR and emails it out. Each company sees only its own loads and inventory, scoped on the server in the query, never in the UI alone.
- Their loads, their inventory, live, nobody else’s
- The daily report becomes a login you hand out once
- Same tickets your scale house already finalized
Every demo carries it: sign in with “See what your customers get” and you land where your customer would.
Tanks in gallons. Bins in bushels.
One codebase. Container terms and units are configuration on your private instance.
Explore BulkTally Yard in your industry.
Explore fictional demo yards for frac sand, cement, fuel, aggregate, and grain. These demos show BulkTally Yard, our inventory and BOL product. Configuration, additional development, and rollout requirements are agreed during scoping.
BulkTally Yard, on your own cloud.
BulkTally Yard runs as a dedicated private instance on your own DigitalOcean account. We agree the configuration, rollout, and support scope with you. Hosting and deployment requirements for custom systems are defined in their proposal.
Private instance on your cloud
You own the DigitalOcean account and the infrastructure. We configure and deploy BulkTally there, not a shared mega-tenant.
Tuned to your yard
Silos or tanks, lb or gallons, ticket prefixes, roles, letterhead, and the labels your crew already uses. We configure it to match how you work.
Process fit, not workarounds
We learn your inbound/outbound flow, customer portal needs, and reporting cadence, then shape screens and defaults around that use case.
Custom development
Need additional workflows or features? We agree the requirements, delivery schedule, development cost, and any ongoing service changes before work begins.
Direct partnership
You’re not filing tickets into a void. You work with the people who built BulkTally to tweak, extend, and keep it honest as the yard changes.
Industry-ready out of the box
Start from a vertical that already fits (sand, cement, fuel, rock, grain), then we refine until it feels like software made for your plant.
Scoped to your operation.
Implementation, ongoing service, and additional development are quoted based on scope. BulkTally Yard and custom TMS implementations are separate engagements with their own requirements and pricing.
A plan for getting you live.
We define the work and quote it before the build begins.
- Workflow scope: the processes, users, and capabilities your team needs
- Configuration & development: product setup and any custom work agreed in the proposal
- Data & integrations: migration and connections scoped to your requirements
- Rollout: a delivery schedule, training, and go-live plan for your team
Support with a defined scope.
Your proposal sets out the recurring service and its cost.
- Software & maintenance: the services included in your agreement
- Support requirements: agreed around your operation and rollout
- Hosting: infrastructure responsibilities and billing made clear up front
- Future development: additional work and any recurring cost changes quoted before approval
Straight answers before the call.
How we scope your project, what the yard product includes, and where custom work fits.
How much does BulkTally cost?
How is BulkTally Yard deployed?
Which industries does BulkTally support?
What does BulkTally Yard do?
Can you build a custom TMS or additional workflows?
Can I see who changed something in BulkTally Yard?
Get specific about the work.
Explore the software, review a documented yard workflow, and work through the questions that shape an implementation.
Yard implementation study
How storage inventory, finalized tickets, and customer access fit together, with actual product screens using demo records.
When do you need a custom TMS?
Separate configuration gaps from custom development and define a useful scope before committing to a build.
Reconcile inventory against load tickets
Understand baselines, signed movements, drafts, and the checks to make when on-hand differs.
Let’s talk about your operation.
Explore a BulkTally Yard demo or tell us about the transportation workflows you need to support. We’ll discuss the fit, implementation requirements, and next steps.
What does your team need?
Tell us whether you’re looking for yard inventory and BOL software, a custom TMS, or another operational workflow. We’ll discuss what fits today and what needs to be scoped and built.