Custom trucking and drayage software in Baltimore: the invoice kept its fields and lost its addressee

Sixteen thousand people, nine at a time

There is a version of this article that opens with the global transportation management systems market and a compound annual growth rate quoted to two decimal places. It would tell a Baltimore carrier with eight trucks nothing at all. So here is the local picture instead, counted rather than modeled, taken from the Census Bureau’s County Business Patterns file for 2023 — still the most recent county‑level release — which we downloaded in full and filtered ourselves on 3 September 2026.

The first thing the file does is separate two businesses that share a gate.

Read the last three rows against the sixth. Maryland’s entire marine cargo handling industry is thirteen companies. Between them they employ 2,033 people, which is 156.4 per establishment — the largest average workplace in the whole table, and more than seventeen times the 9.1 that truck transportation averages. Truck transportation is 1,835 establishments averaging 9.1 people. One side of the fence is a handful of very large employers under long‑term terminal agreements. The other side is nearly two thousand small firms, most of them with fewer than ten people on the payroll.

That asymmetry is the whole commercial logic of this software category, and it is worth stating before we look at a single price. The terminal side buys systems the way a utility buys systems: once, slowly, with a procurement process. The road side buys the way a nine‑person company buys anything — monthly, per seat or per truck, cancellable. Every vendor selling to you has priced accordingly, and every vendor selling to the terminal has not.

The concentration gets sharper when you put the county file next to the state file.

Eight companies in Baltimore City hold 77.0% of the state’s marine cargo handling employment and 91.4% of its payroll, at $68,387 a head against a statewide $57,589. That is the pier, and it is where your containers become your problem. Around it, the Maryland Port Administration reported a 2025 in which the port handled roughly 50 million tons valued at $65.6 billion, 1.1 million twenty‑foot equivalent units across 2,223 vessel calls, 728,225 autos and light trucks, and 887,513 tons of roll‑on roll‑off farm and construction equipment — first in the country in that last category for another year, and second in autos. Weekly container services went from 12 to 15.

Fifty million tons is the headline. The number that matters to a drayage carrier is 1.1 million TEU, because every one of those boxes that moves inland moves on somebody’s chassis behind somebody’s tractor, and the clock on it starts before the driver has been dispatched.

One caveat we will repeat because it matters more here than in most trades: County Business Patterns counts only establishments with paid employees. A large share of this industry is owner‑operators filing a Schedule C and leased‑on drivers receiving a 1099, and none of them appear anywhere in that table. The real count of trucks working out of Baltimore is much larger than 16,650 people would suggest. We think that undercount is itself informative — it is precisely why the products in this category meter the truck and the load rather than the employee.

What the category charges, priced on 3 September 2026

We checked thirty products on one morning from one machine with an ordinary desktop browser user agent. The result is the usual shape for a business‑to‑business software category, only more so.

Eleven of thirty return a 404 on the exact path that every other software category in the world uses for its price list. We have now run this check across more than forty trades for this blog and it is always worth doing, because a 404 is a fact you can date and a rumor is not. Half the figures circulating for products in this category trace back to a comparison article written by a competitor.

Two of those 404s are worth naming individually because they are the products a Baltimore drayage carrier is most likely to have been pitched. PortPro and DrayEasy are both drayage‑native platforms, both have healthy marketing sites, and neither serves a price. Trimble, Geotab and Verizon Connect — three of the largest telematics businesses on earth — do the same. Samsara and Motive, the two products most likely to already be in your cab, each serve a real, working page and neither one prints a subscription rate on it.

We want to be fair about why. Fleet telematics is genuinely priced per vehicle per month on a term contract, with hardware amortized into it, and the number depends on term length and unit count in ways that a single figure would misrepresent. That is a real reason. It is also a reason that applies to almost every business‑to‑business product, and four companies in this table managed to publish anyway.

Where a pricing URL actually goes

The more interesting finding came from following the redirects rather than just recording the status code. Eight of the thirty pricing URLs do not resolve to a page about price at all, and they fail in eight different ways.

The McLeod one is our favorite, and it is not a criticism. /pricing on a transportation software site can legitimately mean freight rating — the software feature that prices a load — rather than what the software costs. McLeod’s redirect is arguably the correct one for its industry, and it is a small reminder that in this trade the word has two meanings and only one of them is on the invoice.

The DrayEasy one is the other end of the scale. The production domain hands you to a subdomain of a website builder, named after last year, which then returns a 404. That is not a pricing decision. That is a site migration that stopped halfway, on a live product, on the page a prospective customer is most likely to click.

Here is what the three who publish actually charge.

Turvo is worth a sentence of credit before we move on. Its page names two tiers, prints “Pricing: Starts at $5,000 / Month” against the first, and “Pricing: Available Upon Request” against the second. Publishing a five‑thousand‑dollar floor takes some nerve, and it is more useful to a reader than a page that says nothing: within four seconds a nine‑person drayage carrier knows this product is not for them, which is exactly what a price list is for.

Before we take Tai’s card apart, one observation about DAT’s that we have not seen anywhere else. DAT’s upgrade prompts do not quote the price of the next tier. They quote the difference: “For only $90 more, you’ll get…”, then “For only $20 more…”, then “For only $90 more…”, then “For only $80 more…”. On the broker side the deltas are $160 and $130.

A price expressed as a delta is a price you cannot compare. It is also, to be scrupulously fair, exactly how a customer already inside the funnel experiences the decision — the question really is “is the next tier worth ninety more dollars,” not “is the tier itself fairly priced.” We are not calling it a trick. We are pointing out that a card built entirely of differences cannot be reproduced by anyone standing outside it, and that a carrier comparing three vendors is standing outside all three.

One line generates almost all of Tai’s ladder

Tai Software’s card is the most complete thing published in this category, and it rewards arithmetic. Look at the last two columns of the table above.

Included shipments are 2, 6, 12, 25 staff logins against 200, 600, 1,200, 2,500 shipments. At every one of the four tiers, included shipments are exactly one hundred times the staff login count. Not approximately. Exactly, at all four.

Tai has written a productivity assumption into its price list: one member of staff handles one hundred shipments a month. That is about five loads per person per working day, and it is a real number about how this work is done, stated in dollars rather than in prose. If your dispatchers move more than five a day you will buy the overage. If they move fewer, you are paying for shipments you will never use.

Because those two allowances move together, the entire card collapses to one variable, and one line fits it.

Two of the four tiers land on the line to the dollar. A third sits $30 above it, which is 1.22% — inside any rounding you would forgive. Only the top tier departs, and it departs downward, by $1,350, or seventeen percent below what the line predicts. That is a real volume discount at the top of the card and it is worth saying so plainly rather than framing it as a deviation.

The marginal rates tell the same story from the other side. Growth to Premium costs $3.6750 per additional included shipment. Premium to Premium + costs $3.5500. Premium + to Pro costs $2.5615. The first two steps are within thirteen cents of each other; the last one is about thirty percent cheaper than either.

We have taken apart published price cards in about forty trades for this blog now, and a straight line through most of a card is uncommon enough to be worth complimenting. It means somebody sat down with a rate and a spreadsheet rather than picking round numbers that felt right. The $275 intercept is the part almost nobody publishes anywhere: it is the fixed cost of having you as a customer at all, separated from the cost of your volume, and it is small.

The one number Tai does not publish, and how far it can be from the others

Every tier on that card carries the phrase “Competitive Overage Pricing.” No rate is attached to it anywhere on the page. That is the single most important number on the card for a growing carrier, and it is the one number missing.

It can, however, be bounded, and the bound is tight.

Suppose the overage rate is r dollars a shipment. A Growth customer doing 600 shipments a month pays $995 + 400r. A Premium customer doing the same 600 pays $2,465. Those two are equal when r = $3.675. Run the same comparison from Growth to Premium + at 1,200 shipments and the break‑even is $3.60.

So Tai’s unpublished overage rate must sit above $3.675 a shipment. If it were any lower, a Growth customer could simply keep paying overage forever and would never have a volume reason to buy Premium — and the middle of Tai’s own ladder would stop making sense on its own arithmetic.

There is a wrinkle here that is more interesting than the bound, and it is the honest reading of the card. The thing that actually forces you up a tier is not the shipment count at all. It is the staff login count. Growth gives you two. A carrier with an owner, two dispatchers and a billing clerk needs four, and no amount of overage buys a third login.

That is the teardown. The meter the card advertises is shipments. The meter that moves you is seats. And because included shipments are hard‑wired at a hundred per seat, a customer whose people are more productive than Tai’s assumption pays twice: once in overage on the shipments, and again for a seat they did not need. A customer whose people are less productive than the assumption pays for allowance they cannot use. Only a customer sitting exactly on five loads per person per day pays what the card says they should.

Twenty fields, and one of them asks a question the rulebook stopped answering

Now to the part no product in this category models, and the reason we chose to write about this trade at all.

If you pull containers out of Seagirt, some fraction of them will generate a demurrage or detention charge. Demurrage is the terminal charging for the ground the box is sitting on. Detention is the equipment owner charging for the box itself once it is off the terminal. Both are per day, both are large, and both arrive as invoices weeks after the fact from parties you may not have contracted with.

Since 28 May 2024 those invoices have been regulated in a way that almost nothing else in American commerce is. The Federal Maritime Commission’s rule at 46 CFR Part 541, adopted under the Ocean Shipping Reform Act of 2022, does not cap the rate, does not limit free time and does not say when a charge is fair. It regulates the document. And it does so at the level of individual fields.

46 CFR 541.6 lists, in four lettered groups plus a pair of certifications, exactly what must appear on or with a demurrage or detention invoice. We counted them.

Twenty items. Now read 46 CFR 541.5, which is one sentence long and is the whole reason the list matters:

“Failure to include any of the required minimum information in this part in a demurrage or detention invoice eliminates any obligation of the billed party to pay the applicable charge.”

Not reduces. Not delays. Not exposes the billing party to a penalty. Eliminates. A missing column on a document voids the debt the document is trying to collect. We have read a great many regulations for this series and we have not found another one that does this so cleanly. It is the single most software‑shaped sentence in American transportation law: the schema is the enforcement mechanism.

The field that lost its definition

Go back to item four. The invoice must state “the basis for why the billed party is the proper party of interest and thus liable for the charge.”

When the rule was written, that question had an answer three inches further down the page. 46 CFR 541.4, headed “Properly issued invoices,” provided that a demurrage or detention invoice could be issued only to the person who contracted with the billing party for the ocean transportation or storage of the cargo, or to the consignee; that it could not be issued to both; and, in subsection (c), that “a billing party cannot issue an invoice to any other person.”

Motor carriers are not on that list, and that was deliberate. The Commission recorded in the preamble that motor carriers “overwhelmingly support the entire rule,” while vessel‑operating carriers “overwhelmingly questioned” it — and the practice this section stopped, ocean carriers billing whichever trucker happened to be holding the container, is the one this trade complains about most.

But the Commission also wrote something in the preamble to the same rule. Responding to a comment, it said that where a motor carrier has directly contracted with an ocean carrier, “nothing in this rule, either in the proposed or final version, prohibits a VOCC from issuing a demurrage or detention invoice to a motor carrier when a contractual relationship exists.”

Those two statements are hard to hold at the same time, and the World Shipping Council said so. On 23 September 2025 the United States Court of Appeals for the District of Columbia Circuit agreed. In World Shipping Council v. Federal Maritime Commission, 152 F.4th 215, the court held that section 541.4 “is arbitrary and capricious because the Commission failed to explain the seeming inconsistency between its contractual‑privity‑based rationale and its categorical bar against billing motor carriers even when in privity with the billing party.” It severed the section and set it aside.

On 29 December 2025 the Commission published a short final rule doing the paperwork: “Remove and reserve § 541.4.” It used the good‑cause exception to skip notice and comment, on the reasoning that the court had already decided the matter and that delay “could lead to confusion, particularly among the regulated public.” The rest of Part 541, it noted, remains in effect.

So here is where a Baltimore drayage carrier stands on 3 September 2026. Every demurrage invoice you receive must still carry twenty pieces of information. Omitting any one of them still eliminates your obligation to pay. One of the twenty is the reason you are the right person to bill. And the section of the Code of Federal Regulations that defined who the right person is has been deleted. The question is still mandatory. The answer is no longer specified.

We want to be careful about what that does and does not mean, because this is the kind of paragraph that gets over‑read. It does not mean anyone can be billed for anything. The underlying statutory prohibitions on unjust and unreasonable practices at 46 U.S.C. 41102 and 41104 are untouched, the Commission’s interpretive rule at 46 CFR 545.5 is untouched, and the Charge Complaint mechanism at 46 U.S.C. 41310 — which puts the burden of establishing reasonableness on the carrier rather than on you — is not only untouched but was expanded on 1 September 2026, two days before we wrote this, by a final rule confirming that a Charge Complaint may be brought through the ordinary complaint process before an Administrative Law Judge or a Small Claims Officer rather than only through the Commission’s streamlined interim procedure.

What it means is narrower and more useful. The bright line went away, and what replaced it is a fact question about your own contracts. Whether you are properly billed now depends on what you signed, with whom, and in what capacity — and that is a question your own records have to answer, invoice by invoice, because nobody else’s system is going to answer it for you.

Five thirty-day clocks, and a sixth that somebody else can start

The timing rules survived the litigation entirely, and they are the part a carrier can act on tomorrow.

Those five clocks run from four different events, and the third row is the one worth reading twice. If a billing party invoices the wrong person and then discovers the mistake, the corrected invoice must still go out within thirty days of the date the charge was last incurred — not within thirty days of realizing the error. Their mistake does not restart your clock. A charge that took them three weeks to mis‑address leaves nine days to re‑address correctly.

Then there is 541.7(c), which is the only place we have seen a regulation model a party that is simultaneously on both sides of the same transaction. A non‑vessel‑operating common carrier receives an invoice and issues one, for the same charge. If its own billed party disputes, the NVOCC may say so upstream, and its billing party “must then provide an additional thirty (30) calendar days for the NVOCC to dispute the charge upon this notice.”

A dispute raised by a party two links down the chain extends a deadline held by a party one link up. That is a clock whose length depends on somebody else’s behavior, and the party who has to prove it was extended is the one in the middle. If you are ever in the middle — and any drayage carrier who has ever quoted door‑to‑door has been — that notice is the record you must keep.

Here is the practical shape of all of this for a carrier with eight trucks. You cannot control what the terminal charges. You can control whether, on the day an invoice arrives, you can answer five questions in under a minute: was it issued within thirty days of the last day charged; does it carry all twenty required items; does the free time it states match the free time you were told; do the days charged match the days the box was actually out; and does the reason it gives for billing you match a contract you actually signed. Four of those five are mechanical. The fifth is the one the court just reopened.

No product on the market does this. Not because it is hard — it is a checklist and a date comparison — but because a demurrage invoice arrives as a PDF or a portal screen, and none of the systems in this category treat that document as a record with a schema. They treat it as an expense to be coded.

A fee schedule where the truck that crosses the line always costs the same

Leave the pier for a moment. There is a second piece of arithmetic in this trade that is worth showing because it is unusually pure, and because it explains a decision every growing carrier makes badly.

The Unified Carrier Registration fee is an annual charge on every motor carrier, private carrier, freight forwarder, broker and leasing company operating in interstate commerce, collected by a participating state and spent on motor carrier safety enforcement. It is set by rule at 49 CFR Part 367, and it is a six‑rung step function on the number of commercial motor vehicles owned or operated.

On 1 September 2026 — the same day as the Commission’s Charge Complaint rule, as it happens — the Federal Motor Carrier Safety Administration adopted the schedule for registration year 2027 and after, effective 1 October 2026.

Now divide each fee by the smallest fleet that lands in its bracket. This is where the schedule stops looking arbitrary.

Across four consecutive schedules and twenty‑four bracket floors, the vehicle that carries you into a bracket costs almost exactly the same amount no matter which bracket it is — never more than $1.75 apart within a single year, even though the fleet sizes at those floors run from one truck to a thousand and one. In the current schedule, three of the six floors are exactly $46.00 to the cent: 138 is three times forty‑six, and 276 is six times forty‑six.

The schedule is not really six prices. It is one price — about $46 today and $55 from October — charged for the truck that crosses a line, with every truck between lines carried free. That is a genuinely elegant piece of fee design, and it is invisible unless you divide.

The consequence for a growing carrier is a set of cliffs that have nothing to do with the cost of anything.

The thousand‑and‑first truck costs $48,617 in registration fees. That is not a Baltimore problem — nobody in this article’s audience is running a thousand tractors — but the same shape at the bottom of the schedule is. Your third truck costs $112 and your fourth and fifth cost nothing. Your sixth costs $166 and your seventh through twentieth cost nothing.

To its credit, the agency says all of this out loud, and we should say so, because we derived the table above before we read the preamble and then found the agency had got there first. Responding to a comment that the structure is regressive against small carriers, FMCSA wrote that “the brackets are arranged such that motor carriers at the smaller end of each bracket do pay more, expressed on a per‑vehicle basis, than motor carriers at the larger end of each bracket,” and that this is unavoidable given the statutory directive at 49 U.S.C. 14504a(f)(1)(C) to have no more than six brackets. Then, two sentences later:

“Similarly, the overall per‑truck cost of registering in 2027 is similar for the smallest motor carriers in each of the six fee brackets at approximately $54.11 to $55.67 per truck, depending on the bracket.”

Those are the exact two endpoints of our 2027 column, to the cent. The invariant is deliberate and the agency states it. What we have not seen anyone publish is that it also held in 2023, 2024 and 2025, at $39.25–$41.00, $35.80–$37.00 and $44.79–$46.00 — four consecutive schedules built to the same rule. The agency’s own footnote traces the bracket structure back to when the fees were first set in 2007, so this is a rule with two decades behind it — and it happens to describe the pricing card of nearly every product in the previous three sections as well.

Your diesel rate is three numbers, and two of them moved in opposite directions on 1 July

One more piece of arithmetic before we get to the local routing rules, because it is the one most likely to be wrong in a spreadsheet somewhere in your office right now.

Maryland’s motor fuel tax is not a constant. The Comptroller redetermines it every year and publishes a chart, and the chart shows the rate as three stacked components rather than as a single figure. Here are the last two years side by side.

The headline everyone read in June was that Maryland’s fuel tax had risen with inflation, on a consumer price index change of about 2.8%. The rate at the rack went up 1.50% for diesel and 1.30% for gasoline. Both of those statements are true, and the gap between them is the table above.

Only the indexed portion of the rate moves with the index, and you can check that against the chart without leaving the page. The gasoline rate’s indexed portion — the 2013 base plus the cumulative CPI effect — went from 33.00 cents to 33.90, a rise of 2.73%. The diesel equivalent went from 33.75 to 34.75, a rise of 2.96%. Both straddle the 2.8% figure, which is what you would expect from a rounded rate. Meanwhile the sales and use tax equivalent component moved the other way, down three tenths of a cent for both fuels. The Comptroller publishes the components separately for exactly that reason: they are computed from different inputs, they need not move together, and this year they did not.

If your fuel tax accrual, your IFTA worksheet or your fuel surcharge formula has 0.4675 written in it anywhere, it went wrong on 1 July and nothing told you. A fuel tax rate is not a constant. It is a value with an effective date, and in Maryland that date is 1 July, decided from an index figure the Bureau of Labor Statistics publishes in May.

For a carrier burning, say, 6,000 gallons a month in Maryland, seven tenths of a cent is $42 a month — not a crisis. The point is not the magnitude. The point is that a value which changes on a published schedule was stored as a literal, and everything downstream of it — the surcharge you bill, the margin you think you have, the quarterly return you file — inherits the error silently. Rate tables want effective dates. All of them, every time.

The routing rules Baltimore adds, and the fields they need

Every routing engine in this category knows about bridge heights, weight limits and hazmat classes. What follows is four Baltimore‑area rules that turn on facts a routing engine does not have, because they are not facts about the road or about the load. They are facts about history, direction, geometry and land use.

The tunnel remembers what the tank used to hold

Hazardous materials through the harbor are governed by COMAR 11.07.01, the Maryland Transportation Authority’s own chapter. Regulation .04 lists eighteen paragraphs of prohibitions covering every hazard class, and the exceptions are written as named substances and weights rather than as classes: propane and other flammable compressed gas in approved containers “not to exceed 10 pounds gross weight per container, and 100 pounds gross weight per vehicle”; motor fuel in approved containers “not to exceed 5 gallons per container and 20 gallons per vehicle”; fusees not exceeding 100 pounds; Class 9 permitted only for oils with a flashpoint of at least 93°C. Radioactive materials are prohibited except for manufactured articles — the regulation names clock dials, electronic tubes, watches, X‑ray machines and smoke detectors.

All of that is complicated, and all of it is at least a function of the load you are carrying. Then comes subsection D, and it is not.

“Tank vehicles which are empty, or which have a residue of not more than 50 gallons, or vehicles transporting empty containers are prohibited from entering any tunnel if they previously transported a prohibited hazardous material” — unless cleaned and purged, or reloaded with something non‑hazardous, or the previous cargo was one of four named classes. And subsection E removes even those escapes for one case: “Tank vehicles used to transport Class 3 flammable liquids, even if empty, are prohibited from entering any tunnel.”

Read that as a database problem. Whether this truck may enter the Fort McHenry Tunnel this afternoon is not a function of this trip’s manifest. It is a function of the trailer’s cargo history, plus whether a cleaning event has occurred since, plus which of four classes the previous cargo fell into. The manifest for the current move can be completely empty and the answer can still be no.

Not one transportation management system we have looked at models a trailer’s previous load as an attribute that constrains the current route. They model the trailer as a resource with a location and a status. The regulation treats it as a resource with a memory.

There is one more detail in this chapter worth knowing, because it is the sort of thing that has quietly aged. Regulation .01B(1) lists the facilities the chapter applies to, and paragraph (e) of that list is the Francis Scott Key Bridge — the crossing that carried hazardous loads around the tunnels until 26 March 2024, and which is being rebuilt. The regulation still names it. A rule that routes prohibited cargo to a bridge that is not currently there is not a scandal; codes are amended slowly and the Authority publishes current restrictions separately. It is a reminder that a jurisdiction table copied out of a regulation once is a snapshot, and snapshots go stale in ways nothing in your system will flag.

Ninety-six inches, one direction, one ramp

COMAR 11.07.02 is five regulations long and it contains the most surprising routing rule in the region.

Regulation .02: “Motor vehicles, semitrailers, and trailers over 96 inches in width may not use the Baltimore Harbor Tunnel Thruway except as specified in Regulation .04.” Regulation .03 says the same of any vehicle pulling tandem trailers.

Ninety‑six inches is eight feet. The standard modern dry van and the standard modern container chassis are 102 inches wide, which is the standard legal maximum on the interstate network. So the ordinary, entirely legal, everywhere‑else‑unremarkable trailer behind your tractor is, on I‑895, an exception vehicle.

Regulation .04 provides the exceptions, and their shape is the interesting part. A vehicle between 96 and 102 inches may use the Thruway southbound only, from the Child Street entrance ramp. Northbound, it may use the Thruway but must exit at Child Street, and only under a hauling permit applied for in writing to the State Highway Administration under COMAR 11.04.01, granted at the Authority’s discretion, for a stated duration, revocable at any time, and with the decision final.

The same truck, the same trailer, the same width. Southbound it is allowed from one named ramp. Northbound it needs a written permit from a different agency and must leave at that same ramp. A routing engine holding “width: 102 in” and “Maryland maximum width: 102 in” will route straight through and be wrong in one of the two directions.

The penalty in Regulation .05 is not a fine. It is diversion: “vehicles operated in violation of these regulations are subject to diversion from the Baltimore Harbor Tunnel Thruway.” You do not get a ticket. You get sent the long way round, with a container on a clock.

Class 6, and the two-hundred-and-fifty-dollar hitch

Now come inside the city line. Baltimore City Code Article 31, § 6‑26(a)(1) provides that no vehicle of Federal Highway Administration Class 6 or higher, and no commercial vehicle, may park, stand or stop longer than one hour continuously on any street, lane or alley in front of or adjacent to any property “used or intended to be used as a residence.” Subsection (a)(2) carves out a vehicle parked to do work for someone within a radius of one block.

The FHWA classification is a thirteen‑category scheme designed so that automatic traffic recorders at the roadside could sort vehicles by axle count and axle spacing. Class 5 is a two‑axle, six‑tire single‑unit truck. Class 6 is a three‑axle single‑unit truck. Class 9 is the ordinary five‑axle tractor‑semitrailer. Baltimore has taken that traffic‑counting taxonomy and made it the threshold in a parking ordinance.

Then look at where the fine is set. § 36‑2(1): parking or standing a vehicle classified as Class 6 or higher in violation of § 6‑26(a) or (b) is punishable by a fine of $500. § 36‑4(1): parking or standing any other vehicle in violation of the same two subsections is punishable by $250.

Two things fall out of that table. The first is that adding a third axle doubles the fine for an otherwise identical parking violation, because the ordinance borrowed its threshold from a scheme that sorts on axles. The second is that attaching a trailer to a pickup creates a $250 exposure out of nothing: subsections (c)(3), (c)(4) and (c)(5) each carry the same proviso in slightly different words — “unless there is a trailer attached,” “unless the pickup truck has a trailer attached,” “unless the panel‑body delivery truck has a trailer attached.” The hitch is the whole difference between exempt and cited.

And then there is that phrase in (a)(1): “used or intended to be used as a residence.” In a rowhouse city where a block can hold a corner store, a vacant, two rehabs and eleven houses, the residential predicate is not a property of the street segment your routing data has. It is a property of individual parcels, and one branch of it is a statement about somebody’s intent. That is not a field anyone can populate reliably, which is exactly why the practical answer is a curated list of known‑safe stops rather than a computed one.

One a.m. to seven a.m., citywide

Subsection (b) of the same section is one sentence, has no geographic limit, and is the one that actually shapes a drayage day:

“Except as otherwise specified in this section, no commercial vehicle may park, stand, or stop between the hours of 1 a.m. and 7 a.m. on any street, lane, or alley of the City.”

Not on residential streets. Not in restricted zones. On any street, lane or alley in Baltimore City, for six hours a night, with the exceptions listed in subsection (c) — emergency and public vehicles, private passenger vehicles, pickups and small panel trucks without trailers, and vehicles engaged in loading as defined in § 1‑1(q).

Port gates open early and long hauls start before dawn, so a meaningful slice of this trade’s work begins inside that window. The rule says park, stand or stop, and $500 is a real number against a drayage move. The operational answer has always been yard space, and yard space near the terminals is the scarcest thing in this business. The software answer is smaller but not nothing: if your dispatch system knows which of your stops are inside the city line and which are not, and knows what time a driver is due to be sitting still, it can tell you which appointments are quietly generating exposure before the tickets arrive. Ours would.

The part no national platform models

Step back from the specifics for a moment, because there is a pattern running through all six of the rules above and it is the same pattern every time.

The demurrage invoice needs a justification field whose domain was deleted by a court. The tunnel needs the trailer’s previous cargo. The Thruway needs the direction of travel and the ramp. The parking fine needs an axle count from a federal traffic‑counting scheme. The residential rule needs a parcel‑level predicate that includes somebody’s intent. The fuel rate needs an effective date rather than a value.

Every one of those is a field. Not a workflow, not an integration, not a report — a field, on a record you already have, that no product in this category ships because no product in this category is built for Baltimore specifically or for any other city specifically. They are built for the median of the whole country, and the median of the whole country has no harbor tunnel with a memory.

This is the argument we make in every one of these articles and it is worth making plainly here too, because it cuts both ways. A national platform is enormously good value for the eighty percent of your operation that is the same as everyone else’s: order entry, dispatch, driver settlements, document capture, invoicing, integrations to the load boards and the accounting package. You should not build any of that, and if you are paying two or three thousand a month for it you are getting a bargain against what it would cost to write.

The twenty percent is where the money is, and it is exactly the part that is local. It is also, almost always, the part currently living in a spreadsheet on one person’s laptop — and that person is usually the owner.

What custom software actually costs

We publish fixed prices, which is unusual in this business and is the single thing readers email us about most. To make the comparison concrete rather than rhetorical, here is the carrier we have been modeling.

Eight power units. Eleven drivers. Four people in the office: an owner who still dispatches, two dispatchers and a billing clerk. Six hundred container moves a month. That is a real Baltimore drayage shop, and we sized the move count at exactly six hundred on purpose — it is Tai’s Premium allowance to the unit, and therefore the largest volume whose bill can actually be computed from the published card. One move more and the overage rate we bounded earlier at above $3.675 starts applying, and nobody outside the company knows what it is.

Notice what happened between those two rows. The smaller carrier pays more per truck — $4,216 against $3,786 — and more per move — $5.27 against $4.21. It is the same regressive shape as the federal fee schedule two sections ago, arising for the same structural reason: both are step functions, and the small operator is standing at the bottom of a step. Nobody designed that to punish small carriers. It falls out of the mathematics of tiers, and it happens in every tiered product in every industry we have looked at.

For scale in the other direction: our eight‑truck model pays $30,288 a year for software and $333 a year in Unified Carrier Registration fees. The software is 91 times the federal registration fee. Whatever is expensive about running trucks in Maryland, it is not the government’s paperwork.

Those crossover figures are short — a prototype costs about six weeks of the subscription, and the full custom app about five months. We are going to argue against the obvious conclusion in a moment, because the honest answer is not “so cancel the subscription.” But we will not pretend the arithmetic says something softer than it does. On the smaller carrier’s $12,648 a year the same three figures are 0.28, 0.47 and 0.95 years, which is a fairer picture of what most readers of this article are actually looking at.

The full package list and what is in each one is on the pricing page, and every price there is the price. We do not quote by the hour and we do not bill for change requests inside the scope we agreed.

What we would build for a Baltimore drayage carrier

Concretely, and in the order we would build it.

First, the invoice checker. A demurrage or detention invoice arrives; you upload the PDF or forward the email. The system extracts the container number, the bill of lading, the free time stated, the days charged, the rate cited and the issue date, then runs the checks the regulation makes available: were all twenty items present; was it issued within thirty days of the last day charged; does the stated free time match what the terminal told you at the time; do the charged days reconcile against your own gate‑in and gate‑out timestamps; and what basis does it give for billing you specifically. It produces a one‑page dispute letter with the discrepancies enumerated and the deadline calculated, and it tracks the thirty days the billing party has to respond. That is the highest‑value week of work available in this trade, and it is a week.

Second, the equipment record with a memory. Every trailer and tank carries its cargo history, its last cleaning event and the derived flag for whether it may currently enter a tunnel. The flag is computed, never typed. When a load is planned, the routing constraint is read from the equipment rather than from the manifest.

Third, the routing predicates as data. The 96‑inch Thruway restriction with its direction and its ramp; the hazmat class table with its named exceptions and weight limits; the city’s one‑a.m.‑to‑seven‑a.m. window; the curated list of legal stops. Each of these is a small table with an effective date and a citation, so that when a rule changes you change one row and know exactly which rule you changed.

Fourth, the rate tables with effective dates. Fuel tax, fuel surcharge, accessorials, per diem, chassis rental. No literal rates anywhere in code. A rate is a row with a start date, an end date and a source, and a quote issued last March is reproducible today with the numbers that applied last March. Half the disputes in this business are about which rate was in force, and that is a data modeling decision, not an argument.

The e‑commerce half: a rate a shipper can see and a move a shipper can book

The half of this that gets ignored is the customer‑facing one, and in drayage it is where the margin is.

Most small carriers in this trade take work by phone and email from three or four brokers, which means the brokers own the customer relationship, the rate and the data. The alternative is not glamorous and it is not hard: a page on your own domain where a shipper can put in an origin, a destination, a container size and a date, and get a real number back — with the accessorials, the chassis terms and the free‑time assumptions stated rather than buried — and then book it.

That is the Online Store package applied to a service business. It is a storefront whose product is a container move. It matters commercially for a reason that has nothing to do with technology: the carrier who can quote in ninety seconds on their own site wins direct shipper work, and direct shipper work is the difference between a business with margin and a business renting capacity to brokers at spot. It also matters for the first three things on the list above, because a booking you took yourself carries the fields you need to check the invoice later. A booking a broker gave you does not.

Build, buy, or leave it alone

Here is the only list in this article, because we would rather write in sentences and this is the one place a list is genuinely clearer.

• Keep renting your telematics and electronic logging — that is a hardware business with a compliance certification attached and you should not touch it. Keep renting your load board. Keep renting your accounting package.
• Keep renting your TMS too, if it is doing its job. Order entry, dispatch boards, driver settlements, document capture and invoicing are commodity software, they are genuinely cheap against what they replace, and rewriting them is the most common expensive mistake in this category.
• Build the layer above it: the invoice checker, the equipment memory, the routing predicates, the effective‑dated rates, the appointment board and your own customer‑facing quoting page. This is the part that is specific to you, specific to Baltimore, and currently living in a spreadsheet.
• Build nothing at all if you have three trucks and one dispatcher. At that size the spreadsheet is correct, the subscription is cheap, and your time is better spent on the phone. Come back when the spreadsheet has an owner and a version number.

Built in Baltimore, yours to keep

We are a small studio of ex‑startup founders. You work directly with the people writing the code, not with an account manager. We quote a fixed price before we start, and the price on the pricing page is the price.

What you get at the end is the repository, the database, the deployment and the documentation. It runs on your infrastructure under your accounts. If you never speak to us again it keeps working, and if you hire an in‑house developer in two years they inherit something ordinary rather than something proprietary. That matters more in this trade than in most, because a drayage business is bought and sold on the quality of its customer relationships and its equipment records, and neither of those should live in a vendor’s multi‑tenant database.

We have written up more than forty Baltimore trades this way now — warehousing and logistics, towing, parking, limousine and black car — and the pattern holds every time. The rented software is fine. The local layer is missing. The gap is worth a fraction of a year’s subscription to close.

Common questions from Baltimore trucking and drayage operators

What information must a demurrage or detention invoice contain?

Twenty distinct items, grouped by 46 CFR 541.6 into four lettered categories plus a pair of certifications. The identifying group requires the bill of lading numbers, the container numbers, the port of discharge for imports, and the basis for why the billed party is the proper party of interest. The timing group requires the invoice date, the invoice due date, the allowed free time in days, the start and end dates of free time, the container availability date for imports, the earliest return date for exports, and the specific dates charged. The rate group requires the total amount due, the applicable tariff or contract rule the daily rate is based on, and the specific rate or rates. The dispute group requires contact information, a digital means such as a URL or QR code pointing to a public description of what a mitigation request must contain, and defined timeframes for requesting and resolving. Finally the invoice must carry statements that the charges comply with the Commission’s rules and that the billing party’s own performance did not cause or contribute to the charge.

What happens if a demurrage invoice is missing a required field?

The obligation to pay disappears. 46 CFR 541.5 reads in full: “Failure to include any of the required minimum information in this part in a demurrage or detention invoice eliminates any obligation of the billed party to pay the applicable charge.” It is not a penalty and it is not a discount — the charge stops being collectible. Separately, 541.7 provides that an invoice issued more than thirty calendar days after the date the charge was last incurred is one the billed party “is not required to pay.” Whether a particular invoice satisfies the rule is a question of fact, and a carrier who thinks a charge is not owed should take that specific invoice to counsel rather than relying on a general description in a blog post.

Can an ocean carrier bill a trucking company for demurrage or detention?

That question no longer has an answer in the Code of Federal Regulations. The February 2024 rule added 46 CFR 541.4, which allowed an invoice to be issued only to the person who contracted with the billing party for ocean transportation or storage, or to the consignee, and to nobody else. On 23 September 2025 the D.C. Circuit held that section arbitrary and capricious in World Shipping Council v. Federal Maritime Commission, 152 F.4th 215, and severed and set it aside; the Commission removed it from the CFR effective 29 December 2025. Everything else in Part 541 stands, so the invoice must still state the basis for your liability — there is simply no longer a regulation saying who is liable. Practically, that turns the answer into a question about your own contracts, which is a good reason to know where they are.

How much does trucking or drayage software cost in Baltimore?

Very few vendors will tell you. On 3 September 2026 we checked thirty products. Tai Software publishes a complete four‑tier card at $995, $2,465, $4,595 and $7,925 a month. DAT publishes a $59 carrier floor and a $159 broker floor. Rose Rocket publishes a single starting figure of $2,080 and Turvo a floor of $5,000. Eleven products return a 404 on /pricing, three block an ordinary request, four did not answer this machine at all, and eight serve a page with no subscription rate on it — including Samsara and Motive, the two most likely to be in your cab already. Eight of the thirty pricing URLs redirect to something that is not a price list, including a contact form, an acquirer’s product page and an unfinished staging subdomain that then 404s. Our modeled eight‑truck carrier running 600 moves a month pays $2,524 a month, or $30,288 a year, for the part of the stack that has a published price.

Why does adding a third truck raise my federal registration fee so much?

Because the Unified Carrier Registration fee is a six‑rung step function and the third vehicle crosses a rung. Under the 2027 schedule at 49 CFR 367.50, effective 1 October 2026, zero to two vehicles pays $55 and three to five pays $167. The third truck costs $112 on its own, and the per‑vehicle cost goes from $27.50 to $55.67. The shape repeats: the sixth truck costs $166, the twenty‑first costs $830, the hundred‑and‑first costs $4,385, the thousand‑and‑first costs $48,617. Every truck that does not cross a line is free. Divide each fee by its bracket floor and you find the reason: the marginal truck costs about the same at every rung, within $1.56 across the whole 2027 schedule.

What is Maryland’s diesel fuel tax rate in 2026?

47.45 cents a gallon from 1 July 2026, up from 46.75. Gasoline is 46.60, up from 46.00. The Comptroller publishes the rate as three stacked components, and this year two of them moved in opposite directions: the CPI component rose a full cent for diesel while the sales and use tax equivalent fell three tenths of a cent, netting seven tenths of a cent, or 1.50%, in a year when the index itself moved 2.8%. That is why a fuel tax rate should never be a literal in your code. It is a value with an effective date, and the date is 1 July.

Which Baltimore tunnels can my truck use?

It depends on the load, the width, the direction and, for tank vehicles, the previous load. COMAR 11.07.01.04 prohibits most hazard classes from the Fort McHenry Tunnel on I‑95 and the Baltimore Harbor Tunnel on I‑895, with carve‑outs written as named substances and weight limits. Subsection D then bars an empty tank vehicle, or one with a residue of not more than fifty gallons, if it previously carried a prohibited material — unless it has been cleaned and purged, or reloaded with something non‑hazardous, or the previous cargo was one of four named classes. Subsection E removes even those escapes for tank vehicles used to carry Class 3 flammable liquids, which are barred “even if empty.” Separately, COMAR 11.07.02 bars vehicles over 96 inches wide, and vehicles pulling tandem trailers, from the Baltimore Harbor Tunnel Thruway except southbound from the Child Street entrance ramp, or northbound under a State Highway Administration hauling permit with an exit at Child Street.

Where can a truck legally park in Baltimore City overnight?

Not on the street. Article 31 § 6‑26(b) provides that no commercial vehicle may park, stand or stop between 1 a.m. and 7 a.m. on any street, lane or alley of the City, with exceptions in subsection (c) for emergency and public vehicles, private passenger vehicles, pickups and small panel trucks without a trailer attached, and vehicles engaged in loading. Subsection (a) separately limits any vehicle of FHWA Class 6 or higher, and any commercial vehicle, to one continuous hour in front of or adjacent to a residence. The fine is $500 for Class 6 or higher under § 36‑2(1) and $250 for anything else under § 36‑4(1), so an identical parked vehicle is a $500 ticket or a $250 ticket depending on its axle count.

Sources and method

Every number in this article came from a primary source we retrieved ourselves on 3 September 2026. Market data is the Census Bureau’s County Business Patterns 2023 state and county files, downloaded in full and filtered locally for NAICS 484110, 484121, 484122, 484220, 484230, 488310, 488320 and 488510 — the county‑level API returns nothing useful for these codes, but the flat files are complete. Regulatory text for demurrage and detention is 46 CFR Part 541 as published by the Government Publishing Office, together with the Federal Maritime Commission’s final rules of 26 February 2024, 29 December 2025 and 1 September 2026 in the Federal Register. The registration fee schedules are 49 CFR Part 367 and the Federal Motor Carrier Safety Administration’s final rule of 1 September 2026. Maryland fuel rates are the Comptroller’s own published rate charts for fiscal years 2026 and 2027. Tunnel and width restrictions are COMAR Subtitle 11.07 as published by the Maryland Division of State Documents. City provisions are from the Baltimore City Law Library’s published Article 31. Port volumes are from the Maryland Port Administration as announced by the Governor’s office in March 2026. Pricing was read from vendor pages on the date stated, and the status‑code sweep was run from a single machine with a desktop browser user agent — a 403 or a timeout tells you what that machine saw, not what the vendor offers everyone.

Three limitations worth stating plainly. First, we could not obtain a current published free‑time and per‑diem tariff for Seagirt Marine Terminal; the terminal distributes those through its own portal and its public bulletins are dated, so this article states what the federal rule requires an invoice to disclose rather than what any particular terminal currently charges. Get that schedule from your terminal directly. Second, County Business Patterns counts only establishments with paid employees, which in a trade this full of owner‑operators and leased‑on drivers understates it substantially; we have said so twice on purpose. Third, our arithmetic on Tai Software’s card is a fit to four published points, not a statement about how the company sets prices — it reproduces two tiers exactly and a third within 1.22%, and we would be delighted to be told the real formula.

Where we have drawn a conclusion from regulatory text rather than reporting a settled practice — the consequence of a required field losing its defining section, and the reading of the empty‑tank rule as a constraint on the trailer rather than the load — we have said so in the text. Nothing here is legal advice, and a carrier deciding whether to pay or dispute a specific invoice should take that invoice to their attorney rather than to us.