{"id":17878,"date":"2026-01-28T09:50:21","date_gmt":"2026-01-28T09:50:21","guid":{"rendered":"https:\/\/tenthplanet.in\/idempiere\/?p=17878"},"modified":"2026-07-07T08:03:18","modified_gmt":"2026-07-07T08:03:18","slug":"how-sales-order-creation-from-rfq-works-in-idempiere","status":"publish","type":"post","link":"https:\/\/tenthplanet.in\/idempiere\/how-sales-order-creation-from-rfq-works-in-idempiere\/","title":{"rendered":"How Sales Order Creation from RFQ Works in iDempiere"},"content":{"rendered":"\n

The sales order from RFQ<\/strong> converts a sourcing decision into a customer-facing transaction. It ensures that quoted and procured items are sold consistently to the intended customer, preserving pricing, references, and traceability without re-entering data.<\/p>\n\n\n\n

Role of RFQ in Sales Order Creation<\/strong><\/h2>\n\n\n\n

An RFQ in iDempiere can act as a bridge between purchase and sales<\/strong>. In your flow, the RFQ captures demand from a customer (Nutrition Retailer), sourcing happens from vendors (ATN), and once procurement is aligned, the same RFQ is used to generate the sales order.<\/p>\n\n\n\n

This avoids disconnected sales creation and ensures that:<\/p>\n\n\n\n

    \n
  • The customer identity<\/strong> is preserved<\/li>\n\n\n\n
  • The commercial intent<\/strong> defined in RFQ is respected<\/li>\n\n\n\n
  • Sales and purchase flows remain linked for audit and analysis<\/li>\n<\/ul>\n\n\n\n

    Sales Order Creation Logic<\/strong><\/h2>\n\n\n\n

    Once the RFQ is active and relevant responses are processed, the system allows creation of a sales order directly from the RFQ using the process action.<\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    At this stage, the user selects:<\/p>\n\n\n\n

      \n
    • Document Type<\/strong>: Typically Standard Order<\/em><\/li>\n\n\n\n
    • Confirms the creation process<\/li>\n<\/ul>\n\n\n\n

      The system then generates a new sales order in d<\/strong>raft<\/strong> status.<\/p>\n\n\n\n

      Header Inheritance and Auto-Filled Data<\/strong><\/h2>\n\n\n\n

      The created sales order automatically inherits critical data from the RFQ header and business context.<\/p>\n\n\n\n

      Key behaviors:<\/p>\n\n\n\n

        \n
      • Business Partner<\/strong> is taken from the RFQ business partner section
        In your case, this becomes the Customer (Nutrition Retailer)<\/strong>, not the supplier.<\/li>\n\n\n\n
      • Partner Location and Contact<\/strong> are defaulted from the customer master<\/li>\n\n\n\n
      • Currency, Sales Representative, Organization<\/strong> follow RFQ context<\/li>\n\n\n\n
      • Order Reference<\/strong> clearly indicates linkage back to RFQ<\/li>\n<\/ul>\n\n\n\n

        This ensures that the sales order is commercially aligned without manual re-selection.<\/p>\n\n\n\n

        \"\"<\/figure>\n\n\n\n

        Sales Order Line Handling<\/strong><\/h2>\n\n\n\n

        Unlike purchase order creation, sales order lines are not auto-created<\/strong> from RFQ lines.<\/p>\n\n\n\n

        This is intentional.<\/p>\n\n\n\n

        Reason:<\/p>\n\n\n\n

          \n
        • RFQ lines represent requested<\/em> or quoted<\/em> quantities<\/li>\n\n\n\n
        • Sales orders represent actual selling commitments<\/em><\/li>\n<\/ul>\n\n\n\n

          As a result:<\/p>\n\n\n\n

            \n
          • The sales order is created with empty lines<\/strong><\/li>\n\n\n\n
          • The user manually enters:\n
              \n
            • Product<\/li>\n\n\n\n
            • Quantity<\/li>\n\n\n\n
            • UOM<\/li>\n\n\n\n
            • Price (from Sales Price List or negotiated)<\/li>\n\n\n\n
            • Freight or additional charges if applicable<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n

              This design allows commercial flexibility before committing the sale.<\/p>\n\n\n\n

              Completion and Downstream Sales Flow<\/strong><\/h2>\n\n\n\n

              Once lines are entered and verified, the Sales Order is completed. From this point, standard sales logistics apply.<\/p>\n\n\n\n

              Typical downstream flow:<\/p>\n\n\n\n

                \n
              • Customer Shipment<\/strong>
                Goods are picked from the warehouse where stock was received via purchase order.<\/li>\n\n\n\n
              • Shipment Confirmation<\/strong>
                Includes pick, QA, and customer confirmation steps if configured.<\/li>\n\n\n\n
              • Sales Invoice<\/strong>
                Generated based on invoice rule (e.g., after delivery).<\/li>\n\n\n\n
              • Customer Payment<\/strong>
                Recorded according to payment rule and terms.<\/li>\n<\/ul>\n\n\n\n

                Each step remains fully traceable back to the original RFQ.<\/p>\n\n\n\n

                Purpose and Outcome<\/strong><\/h2>\n\n\n\n

                This mechanism exists to close the loop between sourcing and selling<\/strong>.<\/p>\n\n\n\n

                Business outcomes:<\/p>\n\n\n\n

                  \n
                • Eliminates duplicate data entry<\/li>\n\n\n\n
                • Preserves demand-to-supply traceability<\/li>\n\n\n\n
                • Ensures correct customer, pricing context, and ownership<\/li>\n\n\n\n
                • Supports audit, margin analysis, and lifecycle reporting<\/li>\n<\/ul>\n\n\n\n

                  In practice, the RFQ becomes the commercial anchor<\/strong>, connecting vendor selection, purchasing, inventory, and final customer sales into one controlled workflow.<\/p>\n","protected":false},"excerpt":{"rendered":"

                  The sales order from RFQ converts a sourcing decision into a customer-facing transaction. It ensures that quoted and procured items […]<\/p>\n","protected":false},"author":19,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[33],"tags":[],"class_list":["post-17878","post","type-post","status-publish","format-standard","hentry","category-purchase"],"acf":[],"_links":{"self":[{"href":"https:\/\/tenthplanet.in\/idempiere\/wp-json\/wp\/v2\/posts\/17878","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=17878"}],"version-history":[{"count":1,"href":"https:\/\/tenthplanet.in\/idempiere\/wp-json\/wp\/v2\/posts\/17878\/revisions"}],"predecessor-version":[{"id":19887,"href":"https:\/\/tenthplanet.in\/idempiere\/wp-json\/wp\/v2\/posts\/17878\/revisions\/19887"}],"wp:attachment":[{"href":"https:\/\/tenthplanet.in\/idempiere\/wp-json\/wp\/v2\/media?parent=17878"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/tenthplanet.in\/idempiere\/wp-json\/wp\/v2\/categories?post=17878"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/tenthplanet.in\/idempiere\/wp-json\/wp\/v2\/tags?post=17878"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}