A method for publishing a sales plan and related devices

Abstract

This invention provides a sales plan publishing method and related equipment. The method includes: creating a product demand plan based on a product planning unit list, wherein each product planning unit includes: a planned product name, a planned sales volume, and the hierarchical relationship between products within the planned product list; triggering a sales plan in the demand plan according to a planned time node, wherein the sales plan is determined based on the planned sales time and the planned sales scheme; creating a corresponding time-version sales plan based on the triggered sales plan and publishing an execution notification. This achieves the goal of enabling the system's automatic task module to execute plan creation tasks at fixed time points according to business process settings, avoiding human error and transparently and promptly sharing upstream and downstream task information, thus meeting the needs for efficient and accurate collaborative planning process execution.

Description

Technical Field

[0001] This invention relates to the field of business information management technology, and more specifically, to a method and related equipment for publishing sales plans. Background Technology

[0002] In demand planning scenarios within the retail and FMCG industry, collaborative planning processes are often highly time-sensitive. Each planned task within the process has a specific execution timeframe; delays or omissions at any planned task node will impact subsequent processes. Furthermore, the longer the process, the greater the impact, ultimately affecting the cost and responsiveness of the enterprise's supply chain. However, enterprise supply chains typically rely on manual constraints during collaborative planning processes. When the process is complex and requires a large number of collaborators, delays or information asynchrony are highly likely.

[0003] Therefore, a new technical solution is urgently needed to solve the above problems. Summary of the Invention

[0004] The summary section introduces a series of simplified concepts, which will be further explained in detail in the detailed description section. The summary section of this invention is not intended to limit the key features and essential technical features of the claimed technical solution, nor is it intended to determine the scope of protection of the claimed technical solution.

[0005] In a first aspect, the present invention proposes a method for publishing a sales plan, the method comprising:

[0006] A product demand plan is created based on a list of product planning units, where each product planning unit includes: the planned product name, the planned sales volume of the planned product, and the hierarchical relationship between the products in the planned product list;

[0007] The sales plan in the demand plan is triggered according to the planned time nodes, where the sales plan is determined based on the planned sales time and the planned sales strategy;

[0008] Create a corresponding time-version sales plan based on the triggered sales plan and issue an execution notification.

[0009] Optionally, the above methods also include:

[0010] Configure the corresponding time-version sales plan unit by setting the plan information;

[0011] Configure the corresponding time-version sales plan release type, release start and end time, and re-release frequency by setting task information.

[0012] Optionally, the above methods also include:

[0013] Monitor the execution status of the corresponding time-based sales plan and display it on the user interface. The execution status includes the number of executions and the execution result.

[0014] Based on the execution information, the frequency of repeated releases in the task configuration can be adaptively adjusted or the sales plan can be revoked.

[0015] Optionally, the above methods also include:

[0016] Create a second sales plan based on the planned sales time and the second planned sales strategy;

[0017] Based on the planned timeline, link the first sales and operations plan and the second sales and operations plan, and trigger one of the first sales and operations plan and the second sales and operations plan.

[0018] Optionally, the above method, which triggers the sales plan in the demand plan based on the planned time node, may include:

[0019] Based on the actual sales information of the products after the execution of the sales plan corresponding to the time version of the sales plan, the corresponding time version of the sales plan is adjusted in real time and the execution notification is updated and released to dynamically adjust the sales plan.

[0020] Optionally, the above methods also include:

[0021] Set the corresponding time version sales plan to enabled or disabled. When the corresponding time version sales plan is disabled, the disabled time version sales plan will be automatically skipped when the release is triggered, a log file will be generated, and a notification that the trigger has been skipped will be pushed.

[0022] Optionally, the above methods also include:

[0023] Update execution information based on the execution status of the corresponding time-based sales plan.

[0024] Secondly, embodiments of the present invention also provide a sales plan publishing device, comprising:

[0025] The creation module is used to create a product demand plan based on a product planning unit list. The product planning unit includes: the planned product name, the planned sales volume of the planned product, and the hierarchical relationship between the products in the planned product list.

[0026] The trigger module is used to trigger the sales plan in the demand plan according to the planned time nodes. The sales plan is determined based on the planned sales time and the planned sales strategy.

[0027] The execution module is used to create a corresponding time-version sales plan based on the triggered sales plan and issue an execution notification.

[0028] To achieve the above objectives, according to a third aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium comprising a stored program, wherein the above-described method for publishing a sales plan is implemented when the program is executed by a processor.

[0029] To achieve the above objectives, according to a fourth aspect of the present invention, an electronic device is provided, comprising at least one processor and at least one memory connected to the processor; wherein the processor is configured to invoke program instructions in the memory to execute the above-described method for publishing a sales plan.

[0030] By employing the above technical solutions, embodiments of the present invention provide a method for publishing sales plans. The aim is to address the problem that in current demand planning scenarios within the retail and FMCG industry, enterprise supply chains typically rely on manual constraints during the execution of planning and collaboration processes. When these processes are complex and require a large number of collaborators, delays in execution or information asynchrony are highly likely. This invention creates a product demand plan based on a product planning unit list. Each product planning unit includes: the planned product name, the planned sales volume of the planned product, and the hierarchical relationship between the products within the planned product list. The sales plan is triggered according to planned time nodes, whereby the sales plan is determined based on the planned sales time and the planned sales strategy. A corresponding time-version sales plan is created based on the triggered sales plan, and an execution notification is published. This achieves the goal of creating a product demand plan based on the planned sales volume of the products to be sold, and automatically executing the sales plan creation task according to the time nodes set in the product sales planning process, thereby publishing sales plans for subdivided time periods. This avoids human error, ensures transparent and timely sharing of upstream and downstream task information, and meets the needs for efficient and accurate planning and collaboration process execution.

[0031] The method for publishing the sales plan of the present invention, other advantages, objectives and features of the present invention will be apparent in part from the following description, and in part will be understood by those skilled in the art through study and practice of the present invention. Attached Figure Description

[0032] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit this specification. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:

[0033] Figure 1 A schematic flowchart illustrating a method for publishing a sales plan according to an embodiment of the present invention is shown;

[0034] Figure 2A schematic block diagram of a sales plan publishing device provided in an embodiment of the present invention is shown;

[0035] Figure 3 A schematic block diagram of an electronic device provided by an embodiment of the present invention is shown. Detailed Implementation

[0036] The terms "first," "second," "third," "fourth," etc. (if present) in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus. The technical solutions of the embodiments of this application will now be clearly and completely described in conjunction with the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them.

[0037] According to a first aspect of the present invention, a method for publishing a sales plan is proposed. Figure 1 A schematic flowchart illustrating a method for publishing a sales plan according to an embodiment of the present invention is shown. Figure 1 As shown, the method includes:

[0038] S110. Create a product demand plan based on the product planning unit list, wherein the product planning unit includes: the planned product name, the planned sales volume of the planned product, and the hierarchical relationship between the products in the planned product.

[0039] It should be noted that a product planning unit list can include at least one product planning unit, and a product demand plan can be created based on this list. A demand plan refers to a plan that forecasts future market demand based on the product structure, i.e., the hierarchical and quantitative relationships of products at each level, with each product as the planning object. This plan guides subsequent supply chain planning, preparing for future market demand in advance. A product planning unit includes the name of a single planned product, the planned sales volume of that single planned product within a preset time period, and its hierarchical relationship with higher-level product types.

[0040] For example, a beverage product named Coca-Cola (Christmas Limited Edition) has a demand plan for the eight weeks leading up to December 25th. The next level up from Coca-Cola (Christmas Limited Edition) is the Coca-Cola category. The demand plan for the Coca-Cola category can include the planned demand for Coca-Cola Sugar-Free, Coca-Cola Fiber, Regular Coca-Cola, and Coca-Cola (Christmas Limited Edition) for the eight weeks leading up to December 25th. The next level up from Coca-Cola is the Carbonated Beverages category, and the next level up is the Beverages category. Understandably, each of these categories has its own corresponding demand plan for a given period, which will not be elaborated upon here. Based on the different levels of product planning units mentioned above, a product demand plan for the broader category of beverages can be created.

[0041] S120. Trigger the sales plan in the demand plan according to the planned time nodes, where the sales plan is determined based on the planned sales time and the planned sales scheme.

[0042] It should be noted that the sales plan is determined based on the planned sales time and the planned sales scheme, while the demand plan is only the planned demand for goods within a certain period. Based on the planned demand for goods, when the current time coincides with the start time of the sales plan within the period, the sales plan for the goods in the demand plan is triggered.

[0043] For example, the sales plan for Coca-Cola (Christmas Limited Edition) is as follows: during the period from October 30th to December 25th, a total planned sales volume of 30 million cans of Coca-Cola (Christmas Limited Edition) will be achieved over 8 weeks. The planned discount method is as follows: a 20% discount for new product launch in the first 2 weeks, a 50% discount for the second item in the following 5 weeks (i.e., 2 items are 25% off the regular price), and a discount of only 1 yuan for the second item in the 8th week, which is Christmas week (i.e., 60% off the regular price). The planned price of Coca-Cola (Christmas Limited Edition), i.e., the regular price, is 5 yuan per can.

[0044] S130. Create a corresponding time-version sales plan based on the triggered sales plan and issue an execution notification.

[0045] It should be noted that, as can be understood from step S120, the sales plan can be a total-to-subsidiary structure, or it can be divided into sales plans based on a more granular time dimension according to specific time periods. Sales plans for different time periods can have different planned sales volumes and planned discounts. Based on the sales plans for different time periods, corresponding time-version sales plans can be created, and the plan can be published through message push to prompt the corresponding authorized accounts to execute it. At the same time, the execution status of the published sales plan is updated in the system to ensure the normal flow of business processes and execution efficiency.

[0046] In some embodiments, the sales plan includes plan information and task information, and the method further includes:

[0047] S210. Configure the plan unit in the corresponding time version sales plan by setting the plan information.

[0048] Understandably, the plan configuration information allows configuration of the plan unit list for the sales plan. By setting the plan units selected in the plan unit list, the underlying product demand plan of the sales plan can be directly modified, and the corresponding time-version sales plan will also change accordingly as the sales plan changes.

[0049] For example, the selected planning unit (1368) in the planning unit list is changed to planning unit (1369), where planning unit (1368) is the planning unit corresponding to Coca-Cola (Christmas Limited Edition) and planning unit (1369) is the planning unit corresponding to Coca-Cola Sugar-Free. After the planning unit is changed, the product demand plan changes from the initial Coca-Cola (Christmas Limited Edition) demand plan to the Coca-Cola Sugar-Free demand plan. Consequently, the sales plan and the corresponding time version sales plan created based on the sales plan will be changed accordingly based on the sales time and sales plan of Coca-Cola Sugar-Free. When the sales plan of Coca-Cola Sugar-Free is triggered according to the time node, the time version sales plan corresponding to Coca-Cola Sugar-Free is created and the execution notification is reissued.

[0050] S220. Configure the release type, release start and end time, and repetition frequency of the corresponding time version sales plan by setting task information.

[0051] It should be noted that the release type, start time, end time, and frequency of repeated releases for the corresponding time-based sales plan can be configured. The release type can be set to multiple tasks or a single task. When set to multiple tasks, the corresponding time-based sales plan will be released multiple times within the time period from the start to the end of the release, based on the frequency of repeated releases. This is understandable; when set to a single task, the execution notification will only be released once at the corresponding time node.

[0052] In some embodiments, the above method further includes:

[0053] S310. Monitor the execution status of the corresponding time version sales plan and display it on the user interface. The execution status includes the number of executions and the execution result.

[0054] Understandably, based on the corresponding time-version sales plan issued after step S130, the process end executes the received sales plan upon receiving the aforementioned notification, and a corresponding execution status will be displayed. Based on the issuance frequency of step S220, the status will display the total estimated number of executions, the number of successful executions, and the number of failed executions.

[0055] S320. Based on the execution information, adaptively adjust the repetitive release frequency in the task configuration or reclaim the sales plan.

[0056] It should be noted that in some practical application scenarios, problems may occur at the task execution end, causing the overall process to fail and ultimately leading to sales plan execution blockage or accidents. Therefore, when the number of failures in the execution information of step S310 reaches a preset value, the frequency of repeated releases in step S220 is adaptively adjusted based on the length of time from the plan's release to its execution and the number of execution failures, in order to expedite the execution of the sales plan. If the current time is already close to the plan's release end time, the sales plan is revoked, and execution notifications are no longer issued to avoid conflicts with the sales plan for the next time period.

[0057] For example, the sales plan for Coca-Cola (Christmas Limited Edition) ran from October 30th to December 25th, a total of 8 weeks. The planned discount was a 20% off new product launch during the first two weeks. As of November 4th, this sales plan had not yet been executed, having failed twice. The original execution notification frequency of once every 3 days was adaptively adjusted to once every day. If the sales plan remained unexecuted by November 10th, the end of the original timeframe, it was revoked to prevent conflicts with subsequent sales plans in the next phase.

[0058] In some embodiments, the above method further includes:

[0059] S410. Create a second sales plan based on the planned sales time and the second planned sales scheme.

[0060] It should be noted that in the context of the actual commercial retail industry, market conditions are complex and varied. Even for a well-calculated sales plan, the actual market feedback may deviate from the expected results. Therefore, a second sales plan can be developed as an alternative sales plan. This allows the second sales plan to be released during the planning period to replace the original sales plan, thus achieving the goal of flexibly adjusting the actual sales plan.

[0061] S420: Associate the first sales plan and the second sales plan according to the planned time node and trigger one of the first sales plan and the second sales plan.

[0062] It is understandable that the planned time point has a one-to-many relationship with the first and second sales plans. That is, based on actual business needs, you can choose to trigger either the first or the second sales plan. It should be noted that only one of the two can be triggered at the same time. When automatically triggering a sales plan, if the first sales plan has already been triggered, the time point will be disconnected from the second sales plan to prevent incorrect or duplicate release of execution notifications.

[0063] In some embodiments, the above method, which triggers the sales plan in the demand plan according to the planned time node, may include:

[0064] S510. Based on the actual sales information of the products after the execution of the sales plan corresponding to the time version of the sales plan, adjust the corresponding time version of the sales plan in real time and update and release the execution notification to dynamically adjust the sales plan.

[0065] It should be noted that this step is a method of dynamically adjusting the sales plan based on market feedback generated from the published sales plan. This is different from the second sales plan in step S420. This step is a method of fine-tuning the planned price and planned discount of the goods based on market feedback in the sales plan formulated on the basis of the sales plan.

[0066] For example, Coca-Cola's (Christmas Limited Edition) sales plan sets a new product launch discount of 20% for the first two weeks after its launch. The planned sales volume within the two weeks is 4.2 million cans, averaging about 300,000 cans per day. Real-time sales information is monitored, and when market feedback indicates that sales volume is significantly lower than 300,000 cans for a consecutive number of days, the discount is automatically adjusted to 25%, and an updated sales plan execution notification with the adjusted discount is issued to allow for real-time adjustments to the sales plan within that time period.

[0067] In some embodiments, the above method further includes:

[0068] S610. Set the corresponding time version sales plan to enabled or disabled. When the corresponding time version sales plan is disabled, automatically skip the disabled corresponding time version sales plan and generate a log file when triggering the release, and push a reminder that the trigger has been skipped.

[0069] It should be noted that the corresponding time-version sales plan set to "enabled" is associated with the module used for release. When the corresponding time-version sales plan is enabled, the release execution notification will be sent normally when the system time coincides with the start time of the corresponding time-version sales plan. When the corresponding time-version sales plan is disabled, the release execution notification will automatically skip the corresponding time-version sales plan in the disabled state. Specifically, if A is a sales plan for 13 weeks before launch and is enabled, and B is a sales plan for 8 weeks before launch and is disabled, and sales plan A is released and successfully executed on time, the execution notification for sales plan B should be released 5 weeks later. However, because plan B is disabled, the release of plan B will be skipped, and a notification message will be pushed to indicate that sales plan B has been disabled and there is currently no sales plan to be released. This is to prevent accidental disabling from causing the sales plan to fail to be released on time. At the same time, a log file will be generated. The log file may include the time when the plan was disabled, the ID of the account subject that performed the disabling operation, the account type, and the remarks when disabling the operation.

[0070] In some embodiments, the above method further includes:

[0071] S710: Update execution information based on the execution status of the corresponding time version sales plan.

[0072] Understandably, according to the execution notification of the corresponding time version sales plan issued in step S130, relevant systems / personnel will subsequently execute the sales plan corresponding to the notification. Regardless of whether the sales plan corresponding to the notification is successfully executed, feedback will be provided on whether it has been executed or not, and the execution information will be updated to confirm which specific nodes of the process have not been executed, resulting in longer process execution time. This will facilitate contacting the execution entities corresponding to the nodes that have not been executed, thereby speeding up the overall smoothness of the sales plan execution and meeting the timeliness of the sales plan under actual business needs.

[0073] It should be noted that, as a response to the above... Figure 1 In addition to the implementation of the methods shown in various related embodiments, this embodiment of the invention also provides a sales plan publishing device for the above-mentioned... Figure 1 The methods described in the above embodiments are used for implementation. This sales plan publishing device embodiment corresponds to the aforementioned sales plan publishing method embodiment. For ease of reading, this sales plan publishing device embodiment will not repeat the details of the aforementioned method embodiments one by one, but it should be clear that the device in this embodiment can correspondingly implement all the contents of the aforementioned method embodiments. Figure 2 A schematic block diagram of a sales plan publishing device provided by an embodiment of the present invention is shown. Figure 2As shown, the device for releasing the sales plan includes:

[0074] Create module 21, which is used to create a product demand plan based on a product planning unit list. The product planning unit includes: the planned product name, the planned sales volume of the planned product, and the hierarchical relationship between the products in the planned product list.

[0075] Execution module 23 is used to create a corresponding time-version sales plan based on the triggered sales plan and issue an execution notification.

[0076] The processor contains a kernel, which retrieves the corresponding program units from memory. One or more kernels can be configured, and adjusting kernel parameters allows for the implementation of sales plan release methods. This addresses the issue that in most testing requirements, the interaction of scenarios often has specific requirements, and existing testing methods cannot meet these business needs.

[0077] This invention provides a storage medium storing a program that, when executed by a processor, implements a method for publishing a sales plan.

[0078] This invention provides a processor for running a program, wherein the program executes a method for publishing a sales plan during runtime.

[0079] This invention provides an electronic device. Figure 3 A schematic block diagram of an electronic device 30 provided in an embodiment of the present invention is shown. Figure 3 As shown, the device includes at least one processor 31, at least one memory 32 connected to the processor 31, and a bus 33; wherein the processor 31 and the memory 32 communicate with each other through the bus 33; the processor 31 is used to call program instructions in the memory 32 to execute the above-mentioned sales plan release method.

[0080] The devices mentioned in this article can be servers, PCs, tablets, mobile phones, etc.

[0081] This application also provides a computer program product, which, when executed on a data processing device, is suitable for executing a program that initializes the following method steps:

[0082] A product demand plan is created based on a list of product planning units, where each product planning unit includes: the planned product name, the planned sales volume of the planned product, and the hierarchical relationship between the products in the planned product list;

[0083] The sales plan in the demand plan is triggered according to the planned time nodes, where the sales plan is determined based on the planned sales time and the planned sales strategy;

[0084] Create a corresponding time-version sales plan based on the triggered sales plan and issue an execution notification.

[0085] Furthermore, the above methods also include:

[0086] Configure the corresponding time-version sales plan unit by setting the plan information;

[0087] Configure the corresponding time-version sales plan release type, release start and end time, and re-release frequency by setting task information.

[0088] Furthermore, the above methods also include:

[0089] Monitor the execution status of the corresponding time-based sales plan and display it on the user interface. The execution status includes the number of executions and the execution result.

[0090] Based on the execution information, the frequency of repeated releases in the task configuration can be adaptively adjusted or the sales plan can be revoked.

[0091] Furthermore, the above methods also include:

[0092] Create a second sales plan based on the planned sales time and the second planned sales strategy;

[0093] Based on the planned timeline, link the first sales and operations plan and the second sales and operations plan, and trigger one of the first sales and operations plan and the second sales and operations plan.

[0094] Furthermore, the above method, which triggers the sales plan in the demand plan based on the planned time nodes, can include:

[0095] Based on the actual sales information of the products after the execution of the sales plan corresponding to the time version of the sales plan, the corresponding time version of the sales plan is adjusted in real time and the execution notification is updated and released to dynamically adjust the sales plan.

[0096] Furthermore, the above methods also include:

[0097] Set the corresponding time version sales plan to enabled or disabled. When the corresponding time version sales plan is disabled, the disabled time version sales plan will be automatically skipped when the release is triggered, a log file will be generated, and a notification that the trigger has been skipped will be pushed.

[0098] Furthermore, the above methods also include:

[0099] Update execution information based on the execution status of the corresponding time-based sales plan.

[0100] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and / or device can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0101] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0102] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0103] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0104] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit it. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A method for issuing a sales plan, characterized in that, include: A product demand plan is created based on a product planning unit list, wherein the product planning unit includes: the planned product name, the planned sales volume of the planned product, and the hierarchical relationship between the products in the planned product list; the sales plan in the demand plan is triggered according to the planned time nodes, wherein the sales plan is determined based on the planned sales time and the planned sales scheme; Create a corresponding time-version sales plan based on the triggered sales plan and issue an execution notification; Also includes: Monitor the execution status of the corresponding time-version sales plan, wherein the execution status includes the number of executions and the execution result; The sales plan is adaptively adjusted or revoked based on the execution information to adjust the frequency of repeated releases in the task configuration. When the number of failures in the execution information reaches a preset value, the frequency of repeated releases is adaptively adjusted based on the length of time from the release of the plan to its execution and the number of execution failures in order to make the sales plan execute as soon as possible. If the current time is close to the end time of the plan's release, the sales plan is revoked and execution notifications are no longer issued. Also includes: A second sales plan is created based on the planned sales time and the second planned sales scheme; Associate the first sales operation plan and the second sales operation plan according to the planned time nodes, and trigger one of the first sales operation plan and the second sales operation plan; The step of triggering the sales plan in the demand plan according to the planned time node includes: Based on the actual sales information of the goods after the execution of the sales plan corresponding to the time version of the sales plan, the corresponding time version of the sales plan is adjusted in real time and the execution notice is updated and released to dynamically adjust the sales plan; that is, based on the sales plan, the planned price and planned discount of the goods are fine-tuned according to market feedback. Also includes: Set the corresponding time version sales plan to enabled or disabled. When the corresponding time version sales plan is disabled, the disabled corresponding time version sales plan will be automatically skipped when the release is triggered and a log file will be generated, and a reminder that the trigger has been skipped will be pushed. The sales plan includes plan information and task information, and the method further includes: Configure the plan unit in the corresponding time version sales plan by setting the plan information; Configure the release type, release start and end time, and re-release frequency of the corresponding time version sales plan by setting the task information; Based on the execution status of the corresponding time-version sales plan, update the execution information, including: providing feedback on whether the process has been executed or not, and then updating the execution information to confirm the specific nodes where the process execution time has increased due to the process not being executed.

2. An apparatus for publishing a sales plan based on the method of claim 1, characterized in that, The device includes: A creation module is used to create a product demand plan based on a product planning unit list, wherein the product planning unit includes: the planned product name, the planned sales volume of the planned product, and the hierarchical relationship between the products in the planned product list; The triggering module is used to trigger the sales plan in the demand plan according to the planned time node, wherein the sales plan is determined according to the planned sales time and the planned sales scheme; The execution module is used to create a corresponding time-version sales plan based on the triggered sales plan and issue an execution notification.

3. An electronic device, characterized in that, It includes a processor and a memory, wherein the memory stores computer program instructions that are executed by the processor to perform the method for publishing a sales plan as described in claim 1.

4. A storage medium storing program instructions that, when executed, perform the method for publishing a sales plan as described in claim 1.

Images