How this is written, and what to do if it is wrong.

Everything here is written by Hamza Rivera. Every post on the blog and every explainer in Receiving 101 carries that byline, and it resolves to a real page about a real person, so you always know who to argue with. The product documentation in the guide is unsigned. It describes how the software behaves, and there is no opinion in it to attribute to anybody.

The about page says what that experience is and, more usefully, where it stops.

Where a page states what the law, a regulation or a standard requires, it links to the statute, the regulation or the standard itself, not to another article about it. Second hand citation is how a wrong figure survives for a decade, passed between blogs that each assumed the last one had checked.

Where something is common practice rather than a legal requirement, it says so in those words. The difference between “the regulation requires” and “carrier tariffs commonly require” is the difference between a fact and a habit, and flattening the two is the most common failure in writing about this trade.

No page here will tell you that receiving errors cost the average manufacturer some specific percentage of revenue. Statistics like that circulate endlessly with no origin anybody can produce, and repeating one would undermine everything around it.

If a number appears on this site it is either from a cited source, or it is a worked example clearly presented as one.

DockCount is a product, and several articles here are about problems it solves. None of them sell it. There is no product block at the end of an article, no aside explaining how we would handle it, and no link out to our own documentation partway down a page somebody is reading because a delivery went wrong. One line sits below the article, after the questions and the sources, and that is the whole of it.

Every template and method here is written to work on paper and in a spreadsheet. Where a page compares options, ours is listed with its real limits alongside the alternatives, including the cases where the right answer is to buy nothing, and that page says plainly who is publishing it.

Templates are on the page. No email address, no form, no download wall. If a page is worth reading it is worth reading without a toll, and a form in front of a blank form is an insult to somebody standing at a loading bay.

Every post on the blog carries the date it was published and the date it was last reviewed. Reviewed means somebody read it again and checked the sources still say what they said, not that a script touched the file to make it look fresh. The explainers in Receiving 101 carry no date. They describe how a job works, and putting a review date on one would imply a check that nobody runs.

Every post is reviewed at least once a year, and immediately when a reader reports an error or a cited source changes.

If something here is wrong, tell us and it gets fixed. A correction that changes the meaning of a page is noted on the page with the date, because silently editing an error away asks every future reader to trust something we have just proved we got wrong once.

Write to support@dockcount.com or use the chat bubble on any page.

This site describes how things generally work in the United States, because that is where most readers are and because the freight and commercial rules are specific enough that trying to write one page for every country would produce a page useful in none.

None of it is legal advice. Your contract with a supplier or carrier can override most of what is described here, and state law varies. For money that matters, ask a lawyer, and the pages that touch the law say so on the page rather than in a footer nobody reads.