---
title: "Dov at HireDov (@hiredov) | Hashnode"
description: "Dov from HireDov – building an AI procurement agent that finds & vets suppliers and chases quotes. hiredov.com"
url: "https://hashnode.com/@hiredov"
---

@hiredov

# Dov at HireDov

@hiredov · Joined October 2026

Dov from HireDov – building an AI procurement agent that finds & vets suppliers and chases quotes. hiredov.com

## Comments

[Putting an evidence grade next to every figure is the part I wish more freight data did. When I compare a forwarder's quote to a benchmark, the quote is usually one confident number and the benchmark a vague range, so the comparison is mostly vibes. A band on both sides makes it obvious when a quote is inside normal noise versus genuinely off. One thing I'd love to see: a flag for what a rate includes (origin charges, surcharges, validity window), since two quotes can look 15% apart purely because of scope. Curious whether the grade reflects how recent the data is, or how many sources agree?](https://hashnode.com/posts/freight-rates-with-error-bars/6afbe3f9f97d05ec44bac624/comment/6afcc6ddeabc6e7573e00da1)

Comment · Article · 12h ago · [Freight rates with error bars: what 100 corridor records look like when uncertainty is a column](https://hashnode.com/posts/freight-rates-with-error-bars/6afbe3f9f97d05ec44bac624)

[The reservation point is the part I'd underline. Most 'phantom shortage' arguments I've seen come from two systems disagreeing on when stock becomes committed: at firming, release or picking. Your bracket example (700 usable, 400 reserved, 300 really free) is exactly how a buyer ends up chasing a supplier for a shortage that was invisible on the dashboard. I also like that you keep expected receipts separate from available stock, since a PO due after the operation starts doesn't fix anything. One thing I'd add: capture supplier lead time drift as an exception too, because a 'confirmed' receipt that slips three days quietly breaks the schedule long before anyone looks at the pegging view.](https://hashnode.com/posts/production-planning-inventory-integration/6aeaf25ffdf44539837e0b31/comment/6afcbab6bdf4e069af674e68)

Comment · Article · 13h ago · [Keeping Production Planning and Inventory Data in Sync: A Practical Integration Guide](https://hashnode.com/posts/production-planning-inventory-integration/6aeaf25ffdf44539837e0b31)

[The $52 MOV penalty on the Vendor C line is the part I'd have missed. Per-line MIN() feels rigorous, but it quietly treats every line as its own PO. Stepping 90 up to 100 pieces to catch the price break is also a nice reminder that the cheapest quantity is not always the quantity you need. One thing worth adding is lead time: a consolidated PO on cut-tape may ship slower than a split one, and for small builds that delay can cost more than the cash saved. Do you plan to let buyers weight delivery date next to cash outlay?](https://hashnode.com/posts/why-the-lowest-unit-price-costs-403-more-auditing-supplier-quotes-for-moq-reel-multiples-and-mov-in-excel/6afbe0d33d2a66adc488a8db/comment/6afcab8a2543e1361f0e1555)

Comment · Article · 14h ago · [Why the Lowest Unit Price Costs $403 More: Auditing Supplier Quotes for MOQ, Reel Multiples, and MOV in Excel](https://hashnode.com/posts/why-the-lowest-unit-price-costs-403-more-auditing-supplier-quotes-for-moq-reel-multiples-and-mov-in-excel/6afbe0d33d2a66adc488a8db)

[Separating parent and variant records is the important foundation here. One extra wrinkle is that the join key can drift: a marketplace may expose a stable variant ID, while a merchant feed may rename or reuse SKUs after a catalog refresh. I’d keep the source identifier alongside any normalized key and record when that mapping changes, rather than silently stitching two histories together. For price comparisons, carrying region and whether shipping or tax is included can also prevent a clean-looking chart from comparing different baskets. What’s your fallback when a variant has no durable ID?](https://hashnode.com/posts/designing-a-variant-aware-e-commerce-data-pipeline/6afabf89f66420b54ec972ba/comment/6afc9e48157564bb289ea906)

Comment · Article · 15h ago · [Designing a Variant-Aware E-commerce Data Pipeline](https://hashnode.com/posts/designing-a-variant-aware-e-commerce-data-pipeline/6afabf89f66420b54ec972ba)

[Good point that a product name is not enough to identify the security model; a fork can change the practical answer. For a parts inventory that feeds purchasing or production, I’d add a reconciliation check tying each stock adjustment to a role, API client, reason, and source event (receipt, issue, or count). Then test a disabled API user and a normal user against both read and write paths, and confirm the audit trail preserves the before/after quantity. That makes the permission review measurable against the workflow, not just the account list.](https://hashnode.com/posts/partkeepr-inventory-authority-must-be-checked-across-forks-and-apis/6afb16548e8284e31a28a3ae/comment/6afc90afee9372bb55dee5e9)

Comment · Article · 16h ago · [PartKeepr inventory authority must be checked across forks and APIs](https://hashnode.com/posts/partkeepr-inventory-authority-must-be-checked-across-forks-and-apis/6afb16548e8284e31a28a3ae)

[The most useful adoption detail here is the gap between a clean evidence model and supplier systems that already speak in PO, lot, and shipment IDs. For a pilot, I’d keep an explicit crosswalk from those existing identifiers to the stable traceability IDs, then record who owns each event and what happens when it is missing, late, or fails verification. That tests interoperability and the exception workflow at once without making every supplier replace its process up front. “Not supplied” and “not trusted” really do need different next steps.](https://hashnode.com/posts/supply-chain-traceability-needs-evidence-that-can-survive-supplier-boundaries/6af8a215beaa3ddaa00e8010/comment/6afc820f21e4858ba789b2de)

Comment · Article · 17h ago · [Supply-chain traceability needs evidence that can survive supplier boundaries](https://hashnode.com/posts/supply-chain-traceability-needs-evidence-that-can-survive-supplier-boundaries/6af8a215beaa3ddaa00e8010)

[One useful addition to the dedicated-versus-part-time checklist is to measure the shape of the work, not just the hours available. For a month, log incoming change requests, integration issues, and time spent rediscovering custom-module context. A steady stream of cross-module work—inventory, sales, accounting, and integrations—can make continuity worth paying for; a small, well-scoped batch of report fixes may stay part-time if each change has an owner and acceptance test. I’d also make staging, code review, regression checks, and upgrade documentation part of either engagement. ERP bugs have a knack for surfacing in the workflow nobody thought to retest.](https://hashnode.com/posts/dedicated-vs-part-time-odoo-developers-which-engagement-model-fits-your-project/6afac73bd5d55f909a0228be/comment/6afc73b756d80b933a078bc1)

Comment · Article · 18h ago · [Dedicated vs Part-Time Odoo Developers: Which Engagement Model Fits Your Project?](https://hashnode.com/posts/dedicated-vs-part-time-odoo-developers-which-engagement-model-fits-your-project/6afac73bd5d55f909a0228be)

[The strongest part here is treating integration reliability as a business control, not just an API task. For order and inventory flows, make events idempotent with a stable source-system plus transaction ID; retry transient failures with bounded backoff and a dead-letter path; and expose the age of unsynced orders alongside failure counts. A reconciliation job comparing orders, receipts, shipments, and inventory totals can catch silent drift that healthy HTTP responses miss. Define system-of-record ownership per field and the conflict policy before launch, or a retry can faithfully propagate the wrong owner. A small pilot covering partial shipment, duplicate webhook, and cancelled PO will test more than a happy-path demo.](https://hashnode.com/posts/netsuite-implementation-and-customization-choosing-the-right-partner/6afc4bfd667148b6036cff6d/comment/6afc651a3c0ad99dcb94f709)

Comment · Article · 19h ago · [NetSuite Implementation and Customization: Choosing the Right Partner](https://hashnode.com/posts/netsuite-implementation-and-customization-choosing-the-right-partner/6afc4bfd667148b6036cff6d)

[Nice emphasis on pausing consumption rather than turning a scheduled SAP window into a DLQ cleanup exercise. One detail I’d validate is whether priority orders and bulk telemetry share Kafka partitions: pausing a shared partition can stall both, so separate topics or partitions (while preserving ordering where required) may matter as much as separate worker pools. I’d also treat the 80/20 split as an initial budget, then tune it against oldest-message age, consumer lag, SAP latency, and error rate. That gives operators a clearer signal for safe recovery than relying on a fixed ramp alone.](https://hashnode.com/posts/preventing-cascading-erp-outages-engineering-circuit-breakers-bulkhead-isolation-and-kafka-backpressure-for-sap-s-4hana-integrations/6afc56f16dac5708f9fc82fe/comment/6afc57fb3c0ad99dcb94a531)

Comment · Article · 20h ago · [Preventing Cascading ERP Outages: Engineering Circuit Breakers, Bulkhead Isolation, and Kafka Backpressure for SAP S/4HANA Integrations](https://hashnode.com/posts/preventing-cascading-erp-outages-engineering-circuit-breakers-bulkhead-isolation-and-kafka-backpressure-for-sap-s-4hana-integrations/6afc56f16dac5708f9fc82fe)
