{"id":18011,"date":"2026-01-30T12:34:25","date_gmt":"2026-01-30T12:34:25","guid":{"rendered":"https:\/\/tenthplanet.in\/idempiere\/?p=18011"},"modified":"2026-08-13T04:55:48","modified_gmt":"2026-08-13T04:55:48","slug":"how-replenish-report-works-in-idempiere","status":"publish","type":"post","link":"https:\/\/tenthplanet.in\/idempiere\/how-replenish-report-works-in-idempiere\/","title":{"rendered":"How Replenish Report Works in iDempiere"},"content":{"rendered":"\n

The replenish report<\/strong> analyzes current stock against replenishment rules per product and warehouse. It evaluates on-hand, min\/max levels, and open orders to determine required quantities, acting as the decision layer between inventory visibility and replenishment execution.<\/p>\n\n\n\n

Replenishment Rules Setup<\/strong><\/h2>\n\n\n\n

Replenishment behavior is driven entirely by configuration maintained in w<\/strong>arehouse<\/strong> \u2192 <\/strong>r<\/strong>eplenish<\/strong> for each product. This setup defines how the report interprets shortages and calculates quantities.<\/p>\n\n\n\n

Each product\u2013warehouse combination stores its own logic, allowing the same product to follow different replenishment strategies in different warehouses. The report reads these rules at runtime; no hard coded logic exists in the report itself.<\/p>\n\n\n\n

Key configuration elements include:<\/p>\n\n\n\n

    \n
  • Replenish Type<\/strong> (e.g., Maintain Maximum Level<\/em>)<\/li>\n\n\n\n
  • Minimum Level<\/strong> and Maximum Level<\/strong><\/li>\n\n\n\n
  • Source Warehouse<\/strong> (for internal transfers)<\/li>\n\n\n\n
  • Default Locator<\/strong> for replenished stock<\/li>\n<\/ul>\n\n\n\n
    \"\"<\/figure>\n\n\n\n

    Stock Evaluation Logic<\/strong><\/h2>\n\n\n\n

    When the report runs, it evaluates inventory using real transactional data. It starts by checking on hand qty<\/strong> from storage records and then adjusts the effective availability by considering quantities already committed or expected.<\/p>\n\n\n\n

    The calculation logic is conservative by design: it avoids over-ordering by accounting for what is already in motion. This ensures replenishment proposals reflect actual future shortages, not just current stock snapshots.<\/p>\n\n\n\n

    Evaluation considers:<\/p>\n\n\n\n

      \n
    • On Hand Qty<\/strong> from storage<\/li>\n\n\n\n
    • Ordered Qty<\/strong> (open purchase or production orders)<\/li>\n\n\n\n
    • Reserved Qty<\/strong> (sales commitments)<\/li>\n\n\n\n
    • Order Pack Qty<\/strong> (rounding rules, if applicable)<\/li>\n<\/ul>\n\n\n\n
      \"\"<\/figure>\n\n\n\n

      Quantity Determination<\/strong><\/h2>\n\n\n\n

      For products using maintain maximum level<\/strong>, the report calculates the required quantity to bring stock back up to the defined maximum. The formula is conceptually simple but applied consistently across all products.<\/p>\n\n\n\n

      If current and incoming stock already meet or exceed the maximum, no replenishment quantity is suggested. If stock is below the target, the difference becomes q<\/strong>ty<\/strong> to <\/strong>o<\/strong>rder<\/strong>.<\/p>\n\n\n\n

      Core calculation logic:<\/p>\n\n\n\n

        \n
      • Qty to Order = Maximum Level \u2212 (On Hand + Ordered \u2212 Reserved)<\/strong><\/li>\n<\/ul>\n\n\n\n

        The result is normalized using Order Pack Qty<\/strong>, ensuring that suggested quantities align with packaging or production constraints.<\/p>\n\n\n\n

        Report Output Interpretation<\/strong><\/h2>\n\n\n\n

        The report output presents one line per product that requires attention. Each line represents a replenishment proposal<\/em>, not an executed transaction. This separation keeps planning and execution clean and auditable.<\/p>\n\n\n\n

        The report clearly shows:<\/p>\n\n\n\n

          \n
        • Product and Warehouse<\/strong><\/li>\n\n\n\n
        • Replenish Type<\/strong><\/li>\n\n\n\n
        • Current stock position<\/strong><\/li>\n\n\n\n
        • Calculated Qty to Order<\/strong><\/li>\n\n\n\n
        • Source Warehouse<\/strong> (when applicable)<\/li>\n<\/ul>\n\n\n\n

          Operational Usage<\/strong><\/h2>\n\n\n\n

          The replenish report is typically used as a planning checkpoint<\/strong> rather than a transactional step. Inventory or procurement teams review the suggested quantities and then decide how to fulfill them\u2014through purchase orders, production orders, or warehouse transfers.<\/p>\n\n\n\n

          Because the report is rule-driven and repeatable, it is often scheduled or reviewed periodically (daily, weekly) to maintain stock discipline without manual recalculation.<\/p>\n\n\n\n

          Common usage patterns include:<\/p>\n\n\n\n

            \n
          • Reviewing shortages before raising bulk purchase orders<\/li>\n\n\n\n
          • Identifying products nearing zero stock despite pending orders<\/li>\n\n\n\n
          • Validating replenishment configuration accuracy across warehouses<\/li>\n<\/ul>\n\n\n\n

            Accounting and Control Boundary<\/strong><\/h2>\n\n\n\n

            The replenish report does not<\/strong> post accounting entries and does not<\/strong> reserve stock. It operates purely as an analytical layer. All financial and inventory impact occurs only when follow-up documents (PO, MM, Production) are completed.<\/p>\n\n\n\n

            This clear boundary ensures:<\/p>\n\n\n\n

              \n
            • No unintended stock movements<\/li>\n\n\n\n
            • No premature accounting impact<\/li>\n\n\n\n
            • Full control over replenishment execution decisions<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"

              The replenish report analyzes current stock against replenishment rules per product and warehouse. It evaluates on-hand, min\/max levels, and open […]<\/p>\n","protected":false},"author":19,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[37,10],"tags":[],"class_list":["post-18011","post","type-post","status-publish","format-standard","hentry","category-idempiere-inventory","category-idempiere-product"],"_links":{"self":[{"href":"https:\/\/tenthplanet.in\/idempiere\/wp-json\/wp\/v2\/posts\/18011","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tenthplanet.in\/idempiere\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/tenthplanet.in\/idempiere\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/tenthplanet.in\/idempiere\/wp-json\/wp\/v2\/users\/19"}],"replies":[{"embeddable":true,"href":"https:\/\/tenthplanet.in\/idempiere\/wp-json\/wp\/v2\/comments?post=18011"}],"version-history":[{"count":1,"href":"https:\/\/tenthplanet.in\/idempiere\/wp-json\/wp\/v2\/posts\/18011\/revisions"}],"predecessor-version":[{"id":19730,"href":"https:\/\/tenthplanet.in\/idempiere\/wp-json\/wp\/v2\/posts\/18011\/revisions\/19730"}],"wp:attachment":[{"href":"https:\/\/tenthplanet.in\/idempiere\/wp-json\/wp\/v2\/media?parent=18011"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/tenthplanet.in\/idempiere\/wp-json\/wp\/v2\/categories?post=18011"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/tenthplanet.in\/idempiere\/wp-json\/wp\/v2\/tags?post=18011"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}