# Jesus Morales

Jesus Morales shares practical guidance on ecommerce operations, especially inventory management, demand planning, and supply chains for direct-to-consumer brands. Morales's posts also cover broader operations topics such as capacity, quality, and scaling processes.

- Profile: https://b2binfluencer.marketing/creators/jesus-morales/
- LinkedIn: https://www.linkedin.com/in/engrjesusmorales
- LinkedIn followers: 1,441
- Topics: ecommerce, supply-chain, lean-manufacturing, inventory-management
- Based on 21 dated posts, latest 2026-10-07

## Summary

Jesus Morales is most useful for practical ecommerce operations guidance on inventory, demand planning, and supply chains.

- Best for: Mid-market DTC brands with stockouts and overstock seeking operations audits or workflow reviews.
- Not for: Sponsorship campaigns needing media kit, rate card, impressions target, or video assets.
- Check first: Confirm fees, scope, turnaround, deliverables, engagement data, and audience demographics before contacting.

### Takeaways

- Effective capacity is like a glass that should not be filled to the rim.
- AI forecasts depend on clean data and planners who judge when to override.
- Reorder points should be recalculated per SKU and channel when conditions change.

## Main ideas

- **Forecast accuracy is a planning-architecture problem**: Morales argues that many DTC brands cannot predict next month's sales within 70 percent, leaving reorder, cash, and inventory decisions to a number that is wrong about a third of the time. They see the deeper issue as a disconnect: revenue plans live in spreadsheets while reorders run on intuition. Their recommendations include a bottoms-up SKU-level forecast built on trailing sell-through and a seasonal index, safety stock sized to each supplier's actual lead-time variability rather than a flat buffer, and weekly reviews. They also call for daily refreshes and anomaly detection around events such as BFCM and product drops.
- **AI forecasting is only as good as the data and the planner using it**: Morales sees machine-learning forecasting as useful but conditional. They write that these models can improve accuracy by 10 to 20 percent over spreadsheet-based forecasting, but only when sales history, lead times, and SKU mapping are clean. A model trained on bad inputs can be worse than no forecast because it looks precise. In their account, planners shift from building forecasts manually to judging when a forecast is trustworthy and when to override it.
- **Inventory visibility is an operating architecture problem, not a sync-app problem**: Morales argues that only about one-third of US and UK retailers report excellent inventory visibility across channels and warehouses, leaving most teams to make purchasing, fulfillment, and cash decisions with data they do not fully trust. Symptoms include overselling when channel counts go stale, manual reconciliation, phantom inventory nobody can locate, and stockouts on hero SKUs while dead stock sits in the warehouse. Their fix is operational architecture: a single source of truth, near-real-time updates instead of batch windows, clear rules for bundles, returns, and preorders, and reconciliation built into a weekly cadence.
- **Reorder points should be recalculated per SKU and channel when conditions change**: Morales pushes back on fixed reorder intervals, such as reordering every 30 to 45 days. They call this a habit that works until it does not: supplier lead times change, channel velocity shifts, and new products behave differently from established sellers. Their approach is to calculate every SKU and channel individually and revisit those settings whenever something upstream changes, rather than on a fixed calendar.
- **Cycle counting and ABC tiering turn inventory accuracy into a routine**: Morales contrasts a once-a-year inventory count with cycle counting, a rolling schedule that counts a small slice of SKUs every day or week. They recommend tying count frequency to product importance: count top sellers monthly, mid-tier products quarterly, and slow movers once or twice a year. This applies the same ABC tiering they use for safety stock to the counting process.
- **Peak-season risk often starts inside the operation and with published carrier costs**: Morales argues that peak-season planning still focuses on whether there will be enough trucks, but the bigger risk often lies in an order stalling before freight. A shipment can be allocated, picked, and packed, then sit because of a gap between the ERP, the warehouse floor, the shipping station, and a compliance check. A few hundred orders stuck this way create a backlog even when trucks, labor, and inventory are available. The same post notes that 3PLs allocate carrier capacity based on who gives them volume projections in advance, so brands that wait until October get whatever is left.
- **A second warehouse is a total-cost decision, not a shipping-rate decision**: Morales challenges the assumption that going from one warehouse to two cuts shipping costs in half. They acknowledge that positioning inventory closer to customers can shorten delivery distances and cut per-order shipping costs, especially before peak. But safety stock must now exist at each location, typically adding 15 to 25 percent to total inventory carrying costs for anything stocked at more than one node. Add systems work for a unified inventory view and staff time to manage rebalancing, and the math only works past a certain order volume.
- **Respect system limits and match process strategy to volume and variety**: Morales teaches operations fundamentals through simple examples. They distinguish design capacity, the maximum output a system is built to handle, from effective capacity, the output it can realistically sustain after accounting for maintenance, breaks, and late materials. Managers who expect design capacity every day burn out teams; efficiency is actual output divided by effective capacity. They also argue that process strategy must match volume and variety: job shops for low volume and high variety, batch flow for the middle, and continuous flow for high volume and no variety. Facility layout follows the same logic, with product-oriented layouts built for speed and process-oriented layouts for flexibility.
- **Pay for prevention; produce only when demand pulls**: Morales argues that cutting corners on quality does not save money; it shifts costs from prevention to external failure. They outline four quality-cost buckets: prevention, appraisal, internal failure, and external failure. Prevention—training, process planning, and product design—is the cheapest place to spend, while external failure brings warranty claims, recalls, lawsuits, and reputational damage. In a separate post, they contrast push systems, where a business builds to a forecast and pushes product into a warehouse, with pull systems, where production starts only in response to actual customer demand. They credit Toyota with the pull model and describe kanban signals triggering replenishment when material runs low. Pull systems, they say, require trust in suppliers and a fast production process.
- **Mid-market DTC brands face a specific margin squeeze**: Morales cites the 2026 Ecommerce P&L Benchmark Report to describe pressure in the $10M to $50M revenue cohort. Brands under $10M grew 24 percent on average and brands over $50M grew 41 percent, while the middle cohort declined 4.6 percent. EBITDA in that middle band dropped from 10 percent to 7.25 percent, contribution margin compressed nearly 6 percent at the median, ROAS declined 9 percent, and fixed marketing costs climbed 32 percent as a share of revenue. They say top performers tracked total customer acquisition cost rather than ROAS alone and kept general and administrative spending lean while revenue was uncertain.

## Work to read

- [Demand planning: connect the forecast to replenishment](https://www.linkedin.com/posts/engrjesusmorales_demandplanning-ecommerceoperations-inventorymanagement-activity-7510348501755686912-MgMF)
- [Cycle counting: catch inventory drift before the annual count](https://www.linkedin.com/posts/engrjesusmorales_dtcoperations-inventorymanagement-supplychain-activity-7506352586472542208-a5xy)
- [Inventory visibility across channels and locations](https://www.linkedin.com/posts/engrjesusmorales_inventorymanagement-ecommerceoperations-dtc-activity-7511062663356055553-P6iU)
- [Reorder points should respond to changing conditions](https://www.linkedin.com/posts/engrjesusmorales_dtcoperations-supplychain-inventorymanagement-activity-7480712460866560000-q7Db)
- [AI forecasting depends on reliable inputs](https://www.linkedin.com/posts/engrjesusmorales_dtcoperations-aiinecommerce-demandplanning-activity-7486042575313801216-gbs6)

## Partnerships

The posts do not advertise a sponsorship package, rate card, or published partnership program. Instead, Jesus Morales repeatedly invites readers to contact them about operations work: auditing a process, reviewing a workflow, or shifting spend from firefighting to prevention. The invitation appears at the end of posts on capacity, quality costs, and scaling, suggesting a consulting-style conversation about a brand’s own operation rather than a menu of sponsored formats. Ask about partnership formats, pricing, and deliverables; the posts do not provide those details.

## Alternatives

- Imran Choudhery, M.S., CSCP: Choose Imran Choudhery over Morales when the engagement is about organizing planning roles or managing inventory for a capital-intensive, asset-heavy operation rather than DTC sell-through. The posts separate demand planning from supply planning and warn that merging the roles produces shortages, expediting, excess inventory, and cash tied up in stock. Another post applies min-max planning to utility operations, covering average usage, storm and emergency demand, supplier lead times, safety stock, storage constraints, and regular parameter review. This is a better fit when the client needs a structured demand-versus-supply planning model or critical-spares and maintenance-inventory discipline.
- Kyle Henson: Choose Kyle Henson over Morales when the problem is physical inventory accuracy rather than forecasting. The posts focus on discrepancies caused by internal consumption that never gets recorded — R&D borrowing components, production cannibalizing finished builds, maintenance taking fasteners — and on manufacturers losing revenue to stockouts while systems show healthy stock. The proposed fix is simple Kanban with QR-coded cards that trigger reorders and capture consumption as people touch inventory. This is a better fit when the client's ERP counts cannot be trusted and the remedy has to work on the shop floor.
- Eric Ciampoli (MBA): Choose Eric Ciampoli over Morales when the buyer wants plant-floor knowledge, documentation, and operational intelligence rather than demand planning. The posts describe ECIC's work in operational improvement, ERP alignment, process optimization, and plant visibility. They present OPSIDIAN as a way to connect plant data, documentation, and knowledge so procedures keep pace with equipment and process changes. This is a better choice when the deliverable is an operations-intelligence or documentation-consistency engagement across a manufacturing site.

---
AI-assisted summary of public posts. Audience demographics are not available. Engagement appears only where we checked recent posts. Method: https://b2binfluencer.marketing/methodology/