Batch processing method and apparatus, electronic device, and readable medium

Abstract

The present disclosure provides a batch processing method and apparatus, an electronic device, and a readable medium. The method comprises: in response to a first configuration operation on a first batch tool of a management page of a target entity, determining target sub-entities and a target main object, the target sub-entities being subordinate entities of the target entity, and the target main object being an object in the target entity; and then, on a management page of the target sub-entities, displaying target sub-objects, which correspond to the target main object, in the target sub-entities, attribute information of the target sub-objects being the same as that of the corresponding target main object. In this way, by one use of the first batch tool, a user operates, in batches, the target sub-objects, which correspond to the target main object, in the target sub-entities, so that the management page of the target sub-entities displays the target sub-objects that belong to the target sub-entities and correspond to the target main object, and the user does not need to operate the target main object and the target sub-objects one by one, thereby improving the efficiency of processing objects in chain entities.

Description

Batch processing method, device, electronic device and readable medium

[0001] This disclosure claims priority to Chinese Patent Publication No. 202410139857.5 filed on January 31, 2024, and the contents of the above-mentioned Chinese Patent Publication are hereby incorporated by reference in their entirety as a part of this disclosure. Technical Field

[0002] The present disclosure relates to a batch processing method, device, electronic device and readable medium. Background Art

[0003] Instant retail is a high-efficiency home consumption format based on an instant delivery system. It is a typical new retail format and new consumption model. Its main characteristics are: consumers place orders on online trading platforms, offline physical retailers accept orders, pick and pack the goods, and then deliver them to the address specified by the consumer, completing the order in about 30 to 60 minutes.

[0004] With the development of instant retail, many chain entities (such as chain merchants) have entered the online trading platforms of instant retail. Chain entities usually have numerous sub-entities (such as stores). The main object of the chain entity's headquarters will correspond to different sub-objects in different sub-entities. To ensure the stable and reliable operation of the instant retail business of the chain entity on the online trading platform, the sub-objects corresponding to the same main object in each sub-entity must have their own identifiers. In other words, each object in a chain entity must have a unique identifier. As a result, when the chain entity processes its own objects, it needs to operate on each object one by one, which is inefficient.

[0005] Summary of the Invention

[0006] In order to solve the above technical problems, the present disclosure provides a batch processing method, device, electronic device and readable medium. By operating the batch tool on the management page of the chain entity, batch processing of sub-objects corresponding to the main object in the sub-entities under the chain entity can be achieved, thereby improving the processing efficiency of the chain entity on objects in the instant retail scenario.

[0007] In order to achieve the above objectives, the technical solutions provided by the present disclosure are as follows:

[0008] In a first aspect, the present disclosure provides a batch processing method, comprising:

[0009] In response to a first configuration operation on a first batch tool on a management page of a target entity, target sub-entities and target primary objects are determined, wherein the target sub-entities are subordinate entities of the target entity, and the target primary objects are objects within the target entity, and the first batch tool is used to batch set primary objects within an entity to the sub-entities;

[0010] On the management page of each target sub-entity, a target sub-object corresponding to the target main object in the target sub-entity is displayed, and the attribute information of the target sub-object is the same as that of the corresponding target main object.

[0011] In a possible implementation, the first batch tool on the management page of the target entity includes a first control for triggering selection of a main object and a second control for triggering selection of a sub-entity, and the first configuration operation includes operating the first control corresponding to the target main object to select the target main object and operating the second control corresponding to the target sub-entity to select the target sub-entity;

[0012] and / or, the first batch tool on the management page of the target entity includes a first control for triggering selection of a main object and a third control for triggering application to all sub-entities, the first configuration operation includes operating the first control corresponding to the target main object to select the target main object and operating the third control to apply to all sub-entities of the target entity, the target sub-entities being all sub-entities included in the target entity;

[0013] And / or, the first batch tool on the management page of the target entity includes a fourth control for triggering the download of a template file and a fifth control for triggering the upload of a template file, the first configuration operation includes operating the fourth control to obtain a first template file and operating the fifth control to upload a second template file, the second template file being the file after the identifier of the target main object and the identifier of the target sub-entity are filled in the first template file.

[0014] In a possible implementation, determining the target sub-entity and the target main object in response to a first configuration operation on a first batch tool on a management page of the target entity includes:

[0015] In response to the first configuration operation, a first main task is generated, where the first main task is used to instruct to make the sub-object corresponding to the target main object effective on the target sub-entity;

[0016] The method further comprises:

[0017] Based on a three-level or higher-level task model, split the first main task into N subtasks, each of the N subtasks being used to instruct a target subobject corresponding to the target main object to take effect in a corresponding target subentity, where N is equal to the number of the target subentities;

[0018] When the execution time of the first main task reaches a preset period, statistics are collected on the execution status of the N subtasks.

[0019] In a possible implementation, the method further includes:

[0020] In response to a second configuration operation on a second batch tool of the management page of the target entity, determining an identifier of an object to be modified and attribute information to be modified, the attribute information to be modified comprising at least one of the following information: title, price, or inventory, the object to be modified comprising a main object and / or a sub-object;

[0021] On the management page of the target entity, the attribute information of the object to be modified after being modified based on the attribute information to be modified is displayed.

[0022] In one possible implementation, the second batch tool on the management page of the target entity includes at least one of the following controls: a sixth control for triggering configuration of attribute information to be modified, a type of object to be modified, and a range of objects to be modified; a seventh control for triggering downloading of a template file; and an eighth control for triggering uploading of a template file. Determining, in response to a second configuration operation on the second batch tool on the management page of the target entity, the identifier of the object to be modified and the attribute information to be modified includes:

[0023] In response to operating the sixth control, displaying a third template file;

[0024] In response to operating the seventh control, downloading the third template file;

[0025] In response to operating the eighth control, the fourth template file is obtained, wherein the fourth template file is a file obtained by filling in the identifier of the object to be modified and the value of the attribute information to be modified in the third template file;

[0026] According to the fourth template file, the identifier of the object to be modified and the attribute information to be modified are determined.

[0027] In a possible implementation, displaying, on the management page of the target entity, the attribute information of the object to be modified after being modified based on the attribute information to be modified, includes:

[0028] If the type of the object to be modified is a main object, then on the management page of the target entity, the attribute information of the main object to be modified is displayed as the attribute information modified based on the attribute information to be modified; and on the management page of a child entity belonging to the target entity, the attribute information of the child object of the main object to be modified in the child entity is displayed as the attribute information modified based on the attribute information to be modified;

[0029] If the type of the object to be modified is a sub-object, and the attribute information to be modified is inventory or price, then on the management page of the sub-entity belonging to the target entity, the price or inventory of the sub-object of the main object to be modified in the sub-entity is displayed as the price or inventory modified based on the attribute information to be modified.

[0030] In a possible implementation, the method further includes:

[0031] In response to a third configuration operation on a third batch tool on the management page of the target entity, displaying an export progress of the corresponding export task on a batch operation record page;

[0032] In response to the export task for the object to be exported being completed, a ninth control for displaying the result download of the export task on the batch operation record page;

[0033] In response to operating the ninth control, an export file corresponding to the export task is downloaded, where the export file includes a value of a preset export field of each object to be exported.

[0034] In one possible implementation, the third batch tool on the management page of the target entity includes at least one of the following controls: a tenth control for triggering selection of a primary object to be exported, an eleventh control for triggering batch export configuration, a twelfth control for triggering selection of a type of object to be exported, and a thirteenth control for triggering export, and the third configuration operation includes operating the tenth control to select the primary object to be exported, operating the eleventh control, operating the twelfth control to select the type of object to be exported, and operating the thirteenth control to trigger the export task.

[0035] In one possible implementation,

[0036] The management page of the target entity also includes a batch operation record tool, and the batch operation record page corresponding to the batch operation record tool includes at least one of the following contents: batch operation personnel, details of the batch operation, the number of main objects involved in the batch operation, or the number of sub-objects involved in the batch operation.

[0037] In one possible implementation,

[0038] The management page of the target entity also includes at least one of the following tools: a batch listing tool, a batch delisting tool, or a batch deletion tool.

[0039] In a second aspect, the present disclosure further provides a batch processing device, comprising:

[0040] a first determining unit, configured to determine, in response to a first configuration operation on a first batch tool on a management page of a target entity, a target sub-entity and a target primary object, wherein the target sub-entity is a subordinate entity of the target entity, and the target primary object is an object in the target entity, and the first batch tool is used to batch set the primary objects in an entity to the sub-entities;

[0041] The first display unit is configured to display, on the management page of each target sub-entity, a target sub-object corresponding to the target main object in the target sub-entity, wherein the target sub-object has the same attribute information as the corresponding target main object.

[0042] In a possible implementation, the first batch tool on the management page of the target entity includes a first control for triggering selection of a main object and a second control for triggering selection of a sub-entity, and the first configuration operation includes operating the first control corresponding to the target main object to select the target main object and operating the second control corresponding to the target sub-entity to select the target sub-entity;

[0043] and / or, the first batch tool on the management page of the target entity includes a first control for triggering selection of a main object and a third control for triggering application to all sub-entities, the first configuration operation includes operating the first control corresponding to the target main object to select the target main object and operating the third control to apply to all sub-entities of the target entity, the target sub-entities being all sub-entities included in the target entity;

[0044] And / or, the first batch tool on the management page of the target entity includes a fourth control for triggering the download of a template file and a fifth control for triggering the upload of a template file, the first configuration operation includes operating the fourth control to obtain a first template file and operating the fifth control to upload a second template file, the second template file being the file after the identifier of the target main object and the identifier of the target sub-entity are filled in the first template file.

[0045] In a possible implementation, the first determining unit is specifically configured to:

[0046] In response to the first configuration operation, a first main task is generated, where the first main task is used to instruct to make the sub-object corresponding to the target main object effective on the target sub-entity;

[0047] The device further comprises:

[0048] a splitting unit, configured to split the first main task into N subtasks based on a three-level or higher-level task model, wherein each of the N subtasks is configured to indicate that a target subobject corresponding to the target main object is effective in a corresponding target subentity, where N is equal to the number of the target subentities;

[0049] The statistics unit is used to count the execution status of the N subtasks when the execution time of the first main task reaches a preset period.

[0050] In a possible implementation, the apparatus further includes:

[0051] a second determining unit, configured to determine, in response to a second configuration operation on a second batch tool on the management page of the target entity, an identifier of an object to be modified and attribute information to be modified, wherein the attribute information to be modified includes at least one of the following information: title, price, or inventory, and the object to be modified includes a main object and / or a sub-object;

[0052] The second display unit is configured to display, on the management page of the target entity, the attribute information of the object to be modified after being modified based on the attribute information to be modified.

[0053] In one possible implementation, the second batch tool on the management page of the target entity includes at least one of the following controls: a sixth control for triggering configuration of attribute information to be modified, an object type to be modified, and an object range to be modified; a seventh control for triggering downloading of a template file; and an eighth control for triggering uploading of a template file. The second determining unit is specifically configured to:

[0054] In response to operating the sixth control, displaying a third template file;

[0055] In response to operating the seventh control, downloading the third template file;

[0056] In response to operating the eighth control, the fourth template file is obtained, wherein the fourth template file is a file obtained by filling in the identifier of the object to be modified and the value of the attribute information to be modified in the third template file;

[0057] According to the fourth template file, the identifier of the object to be modified and the attribute information to be modified are determined.

[0058] In a possible implementation, the second display unit is specifically configured to:

[0059] If the type of the object to be modified is a main object, then on the management page of the target entity, the attribute information of the main object to be modified is displayed as the attribute information modified based on the attribute information to be modified; and on the management page of a child entity belonging to the target entity, the attribute information of the child object of the main object to be modified in the child entity is displayed as the attribute information modified based on the attribute information to be modified;

[0060] If the type of the object to be modified is a sub-object, and the attribute information to be modified is inventory or price, then on the management page of the sub-entity belonging to the target entity, the price or inventory of the sub-object of the main object to be modified in the sub-entity is displayed as the price or inventory modified based on the attribute information to be modified.

[0061] In a possible implementation, the apparatus further includes:

[0062] a third display unit, configured to display, in response to a third configuration operation on a third batch tool on the management page of the target entity, an export progress of the corresponding export task on a batch operation record page;

[0063] a fourth display unit, configured to display a ninth control for downloading a result of the export task on the batch operation record page in response to completion of the export task for the object to be exported;

[0064] A downloading unit is used to download an export file corresponding to the export task in response to operating the ninth control, wherein the export file includes a value of a preset export field of each object to be exported.

[0065] In one possible implementation, the third batch tool on the management page of the target entity includes at least one of the following controls: a tenth control for triggering selection of a primary object to be exported, an eleventh control for triggering batch export configuration, a twelfth control for triggering selection of a type of object to be exported, and a thirteenth control for triggering export, and the third configuration operation includes operating the tenth control to select the primary object to be exported, operating the eleventh control, operating the twelfth control to select the type of object to be exported, and operating the thirteenth control to trigger the export task.

[0066] In one possible implementation,

[0067] The management page of the target entity also includes a batch operation record tool, and the batch operation record page corresponding to the batch operation record tool includes at least one of the following contents: batch operation personnel, details of the batch operation, the number of main objects involved in the batch operation, or the number of sub-objects involved in the batch operation.

[0068] In one possible implementation,

[0069] The management page of the target entity also includes at least one of the following tools: a batch listing tool, a batch delisting tool, or a batch deletion tool.

[0070] It should be noted that the specific implementation method of the device and the technical effects achieved can be found in the relevant description of the method provided in the first aspect or any implementation method of the first aspect.

[0071] In a third aspect, the present disclosure further provides an electronic device, the electronic device comprising: a processor and a memory;

[0072] The memory is used to store instructions or programs;

[0073] The processor is used to execute the instructions or programs in the memory so that the electronic device executes the method provided by the above-mentioned target aspect or any one of the implementations of the target aspect.

[0074] In a fourth aspect, the present disclosure further provides a readable medium storing instructions or programs, which, when executed on a processor, enable the processor to execute the method provided in the above-mentioned target aspect or any one of the implementations of the target aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0075] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following briefly introduces the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments recorded in the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0076] FIG1 is a flow chart of a batch processing method provided by an embodiment of the present disclosure;

[0077] FIG2 is a schematic diagram of a batch product provided by an embodiment of the present disclosure;

[0078] FIG3 is a schematic diagram of another batch product provided by an embodiment of the present disclosure;

[0079] FIG4 is a schematic diagram of another batch product provided by an embodiment of the present disclosure;

[0080] FIG5 is a schematic diagram of a multi-layer task model provided by an embodiment of the present disclosure;

[0081] FIG6 is a schematic diagram of a batch modification provided by an embodiment of the present disclosure;

[0082] FIG7 is a schematic diagram of a batch export provided by an embodiment of the present disclosure;

[0083] FIG8 is a schematic diagram of a batch tool provided by an embodiment of the present disclosure;

[0084] FIG9 is a schematic structural diagram of a batch processing device 900 provided in an embodiment of the present disclosure; and

[0085] FIG10 is a schematic structural diagram of an electronic device 1000 provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0086] With the development of instant retail, many chain entities have entered the online trading platform. Chain entities can be, for example, supermarkets, pharmaceutical companies or clothing companies. Chain entities have multiple sub-entities. For example, supermarket company A has store a1, store a2 and store a3. The online trading platform can refer to an e-commerce trading platform that can be visited by consumers to purchase goods or services. Consumers can view, purchase and other operations on the objects sold in the sub-entities under the chain entity on the online trading platform. For example, when supermarket A enters online trading platform B, supermarket company A has store a1, store a2 and store a3, then consumers can view and purchase goods sold in store a1, store a2 or store a3 through online trading platform B.

[0087] For a chain entity, the chain entity may include at least a headquarters and stores. Optionally, the chain entity may also include a management unit store, which is used to manage some stores. The management authority of the management unit store is controlled by the headquarters, and the authority of the store is jointly controlled by the headquarters and the management unit store, and the control priority of the headquarters is higher. For example, supermarket enterprise A includes headquarters 1, management unit store 1, management unit store 2, store 1, store 2, store 3, store 4 and store 5, wherein store 1 and store 5 are both managed by headquarters 1 and management unit store 1, and store 2, store 3 and store 4 are managed by headquarters 1 and management unit store 2. In the embodiment of the present disclosure, an entity may refer to the headquarters or management unit store of a chain enterprise, and a sub-entity may refer to a store of the chain enterprise.

[0088] In a chain entity, the objects included in the entity are recorded as main objects, and the objects in the child entities are recorded as child objects. A child object corresponds to a main object in the entity, and the attribute information of the corresponding main object and child object is the same. The difference is that since the main object in the entity does not need to be displayed and sold to consumers, the main object does not need to have the two attributes of price and inventory. However, the child object needs to be displayed and sold to consumers. Therefore, in addition to the attribute information included in the main object (such as product name, product image, product shelf life, etc.), the child object also needs to include inventory and price. Assuming that the attribute information of main object 1 in entity A is attribute information 1, the attribute information of sub-object 1 corresponding to main object 1 in a sub-object a of entity A may include: attribute information 1, price = x, inventory = y.

[0089] It should be noted that the main object of an entity may have corresponding sub-objects in each sub-entity, or may have corresponding sub-objects in some sub-entities. The sub-objects included in the sub-entity may completely correspond to the main object included in the entity, or the sub-objects included in the sub-entity may partially correspond to the main object included in the entity. For example, the headquarters of supermarket enterprise A has main product 1, main product 2 and main product 3, and supermarket enterprise A includes store 1, store 2 and store 3. Main product 1 is distributed to store 1, store 2 and store 3, so that store 1 has sub-product 11, store 2 has sub-product 21, and store 3 has sub-product 31; main product 2 is distributed to store 2 and store 3, so that store 2 has sub-product 22, and store 3 has sub-product 32; main product 3 is distributed to store 1 and store 2, so that store 1 has sub-product 13, and store 2 has sub-product 23. In this way, main product 1 has a corresponding sub-object in each store, main products 2 and main products 3 have corresponding sub-products only in some stores, and only the sub-objects in store 2 completely correspond to the main objects of the headquarters of supermarket company A, with three in each store. The sub-objects in the other two stores only partially correspond to the main objects of the headquarters of supermarket company A.

[0090] In the instant retail scenario, in order to ensure the stability and reliability of the online consumption platform, different objects need to have their own unique identifiers. For example, the main product 1 and its corresponding sub-products 11, 21, and 31 in store 1, store 2, and store 3, respectively, should have four different identifiers so that users (including consumers and staff of the entity and sub-entities) can accurately and uniquely identify the specific object based on the object's identifier. For chain enterprises, the processing of a main object (such as a new main object for a store product) usually requires adaptive processing of the sub-objects corresponding to the main object in some or all stores. However, since each object has a unique identifier, the processing of objects within the chain entity currently needs to be performed one by one, and the processing speed is very slow. Especially as more and more chain enterprises enter the online consumption platform and the number of chain stores continues to increase, the staff of the chain enterprises need to perform a large amount of repetitive work on the online consumption platform, which is heavy in workload and low in efficiency. Therefore, it is particularly urgent to develop batch processing tools to cope with the processing of objects within the chain entity.

[0091] Based on this, an embodiment of the present disclosure provides a batch processing method, which may include: in response to a first configuration operation on a first batch tool on the management page of the target entity, determining the target sub-entity and the target main object, the target sub-entity is a subordinate entity of the target entity, and the target main object is an object in the target entity, and the first batch tool is used to batch set the main objects in the entity to the sub-entities; then, on the management page of each target sub-entity, the target sub-object corresponding to the target main object in the target sub-entity is displayed, and the attribute information of the target sub-object is the same as that of the corresponding target main object.

[0092] In this way, for a target entity belonging to a chain entity, when there is a need to batch add sub-objects corresponding to the main object to certain target sub-entities in the target entity, a first batch tool is provided on the management page of the target entity, and the user only needs to perform a first configuration operation on the first batch tool to quickly realize the need, that is, the user uses the first batch tool once, and based on the target sub-entities and target main objects determined by using the first batch tool this time, batch operates the target sub-objects corresponding to the target main object in the target sub-entity, so that the target sub-objects belonging to the target sub-entity and corresponding to the target main object are displayed on the management page of each target sub-entity. The user does not need to operate the target main object and the target sub-object one by one based on the identification of different objects in the chain entity, which overcomes the current problem of poor processing efficiency caused by the inability to batch process objects in the chain entity, improves the processing efficiency of objects in the chain entity, and thus brings convenience to the staff of the chain entity in the instant retail scenario.

[0093] In addition, the disclosed embodiments also provide batch tools with other functions, each of which can implement batch processing of corresponding functions on objects in the chain entity. The first batch tool mentioned above can be understood as a tool for batch distribution of products. Other batch tools may also include, but are not limited to: batch modification tools, batch export tools, batch operation recording tools, batch listing tools, batch delisting tools, or batch deletion tools.

[0094] It should be noted that the subject implementing the batch processing method may be the batch processing device provided in the embodiments of the present disclosure. The batch processing device may be hosted in an electronic device or a functional module of the electronic device. For example, the batch processing device may be a functional module implementing the batch processing function provided in the embodiments of the present disclosure on a work website provided by an online consumption platform to staff of a chain entity or on a server corresponding to the website.

[0095] It should be noted that in the embodiments of the present disclosure, batch addition, batch setting or batch laying can all refer to the same meaning, which can be understood as setting the sub-object in the sub-entity so that the sub-entity includes the sub-object, or setting the main object in the main entity so that the entity includes the main object.

[0096] FIG1 is a flow chart of a batch processing method according to an embodiment of the present disclosure. The method can be applied to a batch processing device, such as the batch processing device 900 shown in FIG9 below.

[0097] As shown in FIG1 , the method may include, for example, the following S101 to S102:

[0098] S101, in response to a first configuration operation on a first batch tool on a management page of a target entity, a target sub-entity and a target main object are determined, wherein the target sub-entity is a subordinate entity of the target entity, and the target main object is an object in the target entity, and the first batch tool is used to batch set the main objects in the entity to the sub-entity.

[0099] In the instant retail scenario, the target entity can refer to the headquarters or any first-level management unit store of any chain enterprise that has a batch processing requirement and is part of an online consumption platform. Target entity staff can log in to the work website provided by the consumption platform using a username-password or username-verification code combination, and manage the target entity through operations on the management page of the work platform.

[0100] In an embodiment of the present disclosure, a management page for a target entity may include multiple tools for batch processing, including at least a first batch tool. The first batch tool, based on its function, may also be referred to as a batch spreading tool. Specifically, the first batch tool spreads target main objects determined in the target entity to be spread to sub-entities to the determined target sub-entities, such that the target sub-entities include target sub-objects corresponding to the target main objects.

[0101] The target sub-entity can refer to several subordinate entities of the target entity. For example, if the target entity is the headquarters of chain enterprise A, the target sub-entity can be any store belonging to chain enterprise A; or if the target entity is any management unit store a of chain enterprise A, the target sub-entities can be several stores belonging to management unit store a of chain enterprise A.

[0102] Target master objects are several objects within the target entity, and target sub-objects are several objects within the target sub-entity. The "master" and "sub" before the objects are names defined to distinguish them. Master objects exist only within the entity, while sub-objects exist only within the sub-entity. Master objects cannot be displayed or sold to consumers, but sub-objects can be displayed and sold to consumers. For example, if chain store A is the target entity, its headquarters includes ten different types of milk: Milk 1 to Milk 10. Milk 1 to Milk 10 can be understood as the 10 master objects of the target entity. If Milk 1 to Milk 8 are distributed to store 1 of chain store A, and store 1 is the target sub-entity, then Milk 1 to Milk 8 can be understood as the 8 sub-objects of the target sub-entity.

[0103] Scenarios for batch distribution of target entities using the first batch tool may include, but are not limited to: Scenario 1, selecting multiple target master objects and configuring them to all target sub-entities of the target entity with one click; Scenario 2, selecting multiple target master objects and configuring them to at least one target sub-entity of the target entity with one click; Scenario 3, selecting one target master object and configuring it to multiple target sub-entities of the target entity. It should be noted that chain businesses typically distribute all master objects to all target sub-entities, and restrict target sub-entities from selling sub-objects by preventing them from switching to the "on the shelf" state or by setting the inventory of sub-objects in the target sub-entity to 0. Therefore, Scenario 3 is less commonly used.

[0104] Regardless of the above three possible scenarios or other scenarios, it is necessary to determine the target sub-entity and the target main object through the first configuration operation on the first batch tool. Therefore, the first configuration operation can be considered as a series of operations that the user needs to perform using the first batch tool to determine the target sub-entity and the target main object.

[0105] In some possible implementations, the first batch tool can provide multiple methods of batch laying for users to choose and use, that is, different batch laying methods correspond to different first configuration operations on the first batch tool. Three possible batch laying methods are introduced below.

[0106] As an example, a first batch tool on a target entity's management page may include at least a first control for triggering selection of a primary object and a second control for triggering selection of a sub-entity. The first configuration operation may then include operating the first control corresponding to the target primary object to select the target primary object, and operating the second control corresponding to the target sub-entity to select the target sub-entity.

[0107] Optionally, in this example, the first batch tool may also include a control a for triggering the configuration of the price and inventory of the target sub-object. The first configuration operation may also include operating control a to implement the configuration of the price and inventory of the target sub-object corresponding to the selected target main object, so that the target sub-entity can directly put the target sub-object with the price and inventory configuration completed on the shelf.

[0108] For example, referring to FIG2 , the first batch tool is the tool corresponding to batch product distribution, the object is the product, the main object is the main product, and the child entity is the store. When the staff of the headquarters or management unit store of the target entity logs in to the instant retail work website, the management page is shown in the upper left corner of FIG2 . Under the product management item, batch tools such as batch product distribution, batch export, and batch modification may be included. When the user clicks the "Batch Product Distribution" button, the management page is shown in the upper right corner of FIG2 . The user can first select the main product to be distributed, and then select the store to be distributed to, and then submit the batch product distribution process. After the user selects the main product on the page shown in the upper right corner of FIG2 , click "Next", and the management page is shown in the lower right corner of FIG2 . After the user selects the store on the page shown in the lower right corner of FIG2 , click "Submit", and the management page is shown in the lower left corner of FIG2 . Among them, the operation of the user selecting the main product on the page shown in the upper right corner of FIG2 corresponds to the operation of the first control in the first configuration operation, and the operation of the user selecting the store on the page shown in the lower right corner of FIG2 corresponds to the operation of the second control in the first configuration operation.

[0109] As shown in the upper right corner of FIG2 , the methods for selecting the main commodities to be distributed include: Method 1, selecting all main commodities; Method 2, selecting main commodities by category; and Method 3, selecting main commodities by commodity identifier (ID).

[0110] For method one, the scope of all main commodities is related to the authority of the department to which the logged-in user currently operating the work website belongs. If the currently successfully logged-in user A belongs to the headquarters, then all main commodities are all main commodities published and sold by the headquarters. If the currently successfully logged-in user A belongs to a certain management unit store, then all main commodities are all main commodities sold in the management unit store.

[0111] For method two, you can first select a category template, and then select a specific category under the selected category template. The logic for selecting a category template by default can be single selection, that is, when there is one effective category template, the category template is selected by default; when there are multiple effective category templates at the same time, the category template that is most recently modified in the effective category template can be selected. After selecting a category template, the process of selecting a specific category may include: first, click "Add products under the category", and the categories in the selected category template will be displayed in a cascade manner on the page in a drawer or other manner; then, select the specific category in the category template, where multiple selections are allowed, and "all categories" are also supported. If "all categories" is selected, all categories under the category template will be selected. If no category is selected, the "OK" button on the page for selecting a specific category cannot be operated; then, click the "OK" button on the page for selecting a specific category to return to the page for bulk shopping. When displaying a category, at least one of the following information can be displayed: category information (the most detailed level of the category) and the number of main products included in the category. It should be noted that when the selected category contains the Mendeleev category and directly mounts products, the number of main products included in the category includes the sum of the number of products under the Mendeleev category and the number of directly mounted products. For example, if the selected category (such as "Hot Pot Essentials") contains 3 Mendeleev categories (a total of 300 products) and directly mounts 30 products, the number of main products included in the category is 330. It should be noted that for the method of selecting main products by category, categories cannot be selected across category templates. That is, when switching category templates, the specific categories selected under the original category template are cleared, and you need to reselect specific categories under the new category template. It should be noted that when "Select by Category" is selected, a pop-up window or prompt can be used to indicate that the category cannot be modified. For example, the prompt text "When choosing to add products by category, please do not modify the category, which may affect the selection of the number of products" can be displayed.

[0112] Method three is applicable to the case where the product ID is known. During the process of entering the main product ID, when you click the "Add Product ID" button, an ID input pop-up window will pop up. This pop-up window is used to prompt the user to enter the rules for the product ID. For example, the text of the pop-up window can be "Please enter the product ID, which can be separated by line breaks or commas. A maximum of x products can be selected at a time", where x is the preset upper limit of the number of products that can be entered at a time. Multiple clicks on the "Add Product ID" button are supported. For example, if you click the "Add Product ID" button for the first time, enter 100 product IDs, and click "OK"; then click the "Add Product ID" button again, enter another 100 product IDs, and click "Confirm", then a total of 200 products will be added in two times. The number of products added this time and the number of products that can be added can be displayed in the input box. For example, the format can be: number of products added this time / number of products that can be added. When limiting the selection of a maximum of 500 main products for a batch of products, if the first pop-up window number is: xx / 500, 150 products will be added; the second pop-up window number can be zz / 350, where xx is the number of products added at the first display time, and zz is the number of products added at the second display time. For the reliability of this method, quantity verification and status verification will be performed, that is, when the number of selected products exceeds the maximum quantity limit (such as 500), it is prohibited to click "OK", and the maximum quantity limit will be highlighted or a pop-up window will be prompted to delete some product IDs; if the added product ID is not in normal sales status, the product ID will be marked in red to avoid displaying product failure after all submissions. When there is a verification error, you may be prompted with "Some product IDs cannot be identified or the product ID is wrong, please modify it and continue to add. You can also click [One-click Clear] to remove the unrecognizable product ID." If the user clicks [One-click Clear], only the correctly identified and existing product IDs will be retained. When the step of entering the product ID is completed, the selected product is displayed on the page in a drawer or other manner. The displayed product information may include at least one of the following information: attribute information (such as product name, product ID, etc.), product price and release date. The displayed content may also include the number of selected products (such as "x products selected"). On this display page, users can click the "Delete" button to delete a single product. On this display page, users can click "Clear Selected" to clear all selected products.

[0113] For all selected main products, you can also set the price and inventory of sub-products in batches. For price settings, the default selection is "Keep consistent with the main product". You can also select "Custom input" and enter a custom price in the displayed input box. For inventory settings, the default inventory is 0. Select "Keep consistent with the main product". You can also select "Custom input" and enter a custom inventory in the displayed input box. A prompt text can be displayed in the input box, such as "Please enter the inventory." When the inventory quantity is not an integer greater than or equal to 0, or when the price is not greater than 0, an error prompt will be given, for example, the incorrect inventory quantity or price will be marked in red, or the reason for the error will be prompted through a pop-up window. Optionally, you can also select the listing status of the sub-product. The options can include default listing and default delisting. If default listing is selected, the sub-product will be listed by default after the sub-product is successfully added. If default delisting is selected, the sub-product will be delisted by default after the sub-product is successfully added.

[0114] In this example, after selecting the main product, if the quantity of the selected main product is 0, you will not be able to click "Next" to continue selecting the target sub-entity. If the inventory of the sub-product is configured, if the configured inventory is less than 0 or is not an integer, you will not be able to click "Next" to continue selecting the target sub-entity.

[0115] Regarding the steps of selecting stores to stock products, it should be noted that the operation of stocking products in batches is only effective in stores that are operating normally and stores that are suspended. Stocking products in batches cannot be achieved for stores in other statuses. Therefore, when using the function of stocking products in batches, a prompt can be given through a pop-up window or prompt message, such as "It is only effective for stores that are operating normally and stores that are suspended. Please confirm the store status in advance."

[0116] As shown in the lower right corner of FIG2 , the methods for selecting stores to which products need to be distributed include: Method 1, selecting all stores; Method 2, selecting stores by management unit; and Method 3, selecting stores by store ID.

[0117] For option 1, the scope of all stores is related to the permissions of the department to which the user currently logged in to operate the work website belongs. If the currently logged-in user A belongs to the headquarters, then all stores under the headquarters will be all stores. If the currently logged-in user A belongs to a specific management unit store, then all stores under the management of the management unit store will be all stores. Optionally, the user can be prompted to "Only add stores to which this account has permissions, a total of xx stores", where the number of stores refers to the number of stores currently open and closed under the current account.

[0118] For method 2, you can first click "Add Store," which will display the organizational hierarchy in a cascading manner, such as a drawer, on the page for the user to select a store. This drawer page only displays stores with permissions controlled by the currently logged-in account. Multiple stores can be selected, or "All Stores" can be selected. If "All Stores" is selected, all stores under the management unit are selected. If no store is selected, the "OK" button on the page for selecting a specific store will be disabled. Then, clicking "OK" on the page for selecting a specific store will return to the bulk store page and display the selected specific store. The store display may display at least one of the following information: store information (such as store name, store ID, etc.), information about the management unit to which it belongs (displaying multi-level categories, separated by " / ", such as "Supermarket A / Region B"), store address, and an action (such as delete). The display may also include the number of selected stores (such as "Selected x stores"). On this display page, users can delete individual stores by clicking the "Delete" button. On this display page, users can clear all selected stores by clicking "Clear Selected."

[0119] Method three is applicable to the case where the store ID is known. During the process of entering the store ID, when you click the "Add Store ID" button, an ID input pop-up window will pop up. This pop-up window is used to prompt the user to enter the store ID rules. For example, the text of the pop-up window can be "Please enter the store ID, which can be separated by line breaks or commas. A maximum of x stores can be selected at a time", where x is the preset upper limit of stores that can be entered at a time. It supports multiple clicks on the "Add Store ID" button. For example, the first time you click the "Add Store ID" button, enter 100 store IDs, and click "OK"; then click the "Add Store ID" button again, enter another 100 store IDs, and click "Confirm", then a total of 200 stores will be added in two times. The number of stores that have been added this time and the number of stores that can be added can be displayed in the input box. For example, the format can be: the number of stores that have been added this time / the number of stores that can be added. When limiting the selection of a maximum of 500 stores for a batch of products at a time, if the first pop-up number is: xx / 500, 150 stores will be added; the second pop-up number can be zz / 350, where xx is the number of stores that have been added at the first display time, and zz is the number of stores that have been added at the second display time. For the reliability of this method, quantity verification and status verification will be performed, that is, when the number of selected stores exceeds the maximum limit (such as 500), it is prohibited to click "OK", and the maximum limit will be highlighted or a pop-up window will be prompted to delete some store IDs; if the added store ID is not in normal operation or is suspended, the store ID will be marked in red to avoid displaying a failure to store products after all submissions are made. When there is a verification error, it may prompt "Some store IDs cannot be identified or the store ID is wrong, please modify it and continue to add. You can also click [One-click Clear] to remove the unrecognizable store ID. If the user clicks [One-click Clear], only the store IDs that are correctly identified and exist will be retained. When the step of entering the store ID is completed, the selected store is displayed on the page in a drawer or other manner, and at least one of the following information is displayed: store information (such as store name, store ID, etc.), store information of the management unit to which it belongs (displaying multi-level classifications, separated by " / ", such as "A Supermarket / B Region"), store address and operation (such as deletion), and the displayed content may also include the number of selected stores (such as "x stores selected"). On this display page, users can click the "Delete" button to delete a single store. On this display page, users can click "Clear Selected" to clear all selected stores.

[0120] In this example, after completing the store selection, if the number of selected stores is 0, you are not allowed to click "Submit".

[0121] After selecting the store, click the "Submit" button to display a pop-up window. The pop-up window can be shown in the lower left corner of Figure 2. The title of the pop-up window can be "Batch product placement submitted successfully" and the body text of the pop-up window can be "Due to the large amount of data, a certain amount of execution time is required. Closing this page will not terminate the batch product placement operation. You can view the operation results in [Batch Operation Record] later." The pop-up window can include two buttons: View Batch Operation Record and Continue Product Placement. If the user clicks "View Batch Operation Record", the page jumps to the display page corresponding to the batch operation result. If the user clicks "Continue Product Placement", it returns to the first step of the page corresponding to the batch product placement, such as the initial state of the batch product placement shown in the upper right corner of Figure 2.

[0122] As another example, a first batch tool on a target entity's management page may include at least a first control for triggering the selection of a primary object and a third control for triggering the application to all sub-entities. The first configuration operation may then include operating the first control corresponding to the target primary object to select the target primary object, and operating the third control to apply the configuration to all sub-entities of the target entity. In this example, the target sub-entities are all sub-entities within the target entity.

[0123] For example, referring to FIG3, the first batch tool is the tool corresponding to the batch product distribution, the object is the product, the main object is the main product, and the child entity is the store. When the staff of the headquarters or management unit store of the target entity logs in to the instant retail work website, the management page is shown in the upper left corner of FIG3. Under the product management item, batch tools such as batch product distribution, batch export, and batch modification may be included. When the user clicks the "Batch Product Distribution" button, the management page is shown in the upper right corner of FIG3, showing all the main products that can be distributed. The user can first select at least one main product to be distributed, and then click "Distribute Products to All Stores" to complete the batch product distribution process. The management page is shown in the lower right corner of Figure 3, and a pop-up window or other means prompts "Confirm to distribute to all stores?". The main text of the pop-up window can be "After the store configuration is successful, the product will be submitted for review and automatically put on the shelves for sale. This operation will only distribute products to stores with permissions under the account. Already configured stores will not be distributed repeatedly." The pop-up window has two operations: "Confirm" and "Cancel"; if the user clicks the "Confirm" button, the management page is shown in the lower left corner of Figure 3, and the "Operation Result" is displayed through a pop-up window or other means. The main text of the pop-up window can be "Store distribution is in progress and will take effect in 3 to 5 minutes. You can view the distribution results in [Batch Operation Records]. Please wait patiently." The pop-up window has two operations: "View Batch Operation Records" and "Close". When the user clicks "View Batch Operation Records", it will jump to the page corresponding to the batch operation record to view the distribution results. When the user clicks "Close", it returns to the first step of the page corresponding to the batch distribution, such as the initial state of the batch distribution shown in the upper right corner of Figure 3.

[0124] Among them, the operation of the user selecting the main product on the page shown in the upper right corner of Figure 3 corresponds to the part of operating the first control in the first configuration operation, and the operation of the user clicking "Distribute products to all stores" on the page shown in the upper right corner of Figure 3 corresponds to the part of operating the third control in the first configuration operation.

[0125] As shown in the upper right corner of Figure 3, the page for batch distribution displays a list of main products that can be selected. The page also includes a general "Distribute Products to All Stores" button. Each main product corresponds to a selection box. Optionally, the operation corresponding to each main product can also include a "Distribute Products to All Stores" option. In this way, when a user wants to distribute a certain main product to all stores, in one case, they can select the selection box corresponding to the main product and then click the general "Distribute Products to All Stores" button to complete the operation of distributing the main product to all stores; in another case, they can also select the selection box corresponding to the main product and then click the "Distribute Products to All Stores" button in the operation options corresponding to the main product to complete the operation of distributing the main product to all stores. When a user wants to distribute multiple main products to all stores, they can select the selection boxes corresponding to the multiple main products and then click the general "Distribute Products to All Stores" button to complete the operation of distributing the multiple main products to all stores.

[0126] In this example, you can add selected main products with certain common characteristics to all stores in batches. If no main products are selected, you cannot click "Add to all stores." You can only click "Add to all stores" after you have selected at least one main product.

[0127] It should be noted that for batch distribution, when the selected main product has been distributed in some stores, the product will no longer be distributed again, and the price and inventory of the sub-products that have been distributed will not be modified according to the set price and inventory (for example: main product A has already distributed sub-product a in store 1, the price of the sub-product is 15 yuan, and the inventory is 20. If you select "main product A" and click "Distribute products to all stores", set the price of all stores to 18 yuan and the inventory to 999", then after the batch distribution operation is completed, the price of sub-product a in store 1 will still be 15 yuan and the inventory will still be 20. The batch distribution operation only affects the price and inventory of the sub-products distributed for the first time.

[0128] It should be noted that batch product placement can also include the operation type of "batch setting of store sub-products".

[0129] It should be noted that when an error occurs, the embodiment of the present disclosure also includes a "Download Results" button. When the user clicks this button, he can download a table containing information such as the error location and error cause, so that the user can analyze the error and maintain the tool.

[0130] If the batch rollout is successful, the store will receive a notification and conduct an inventory count and verification. If the batch rollout fails, a table containing the reasons for the failure can be downloaded. The reasons include factors from both the main product and the store. For example, abnormal store status can be one of the reasons for the batch rollout failure. If the batch rollout fails, the store can be re-run.

[0131] In some possible implementations, for the action of performing the first configuration operation on the first batch tool, the backend (e.g., a server) corresponding to the first batch tool can generate a main task (i.e., a first main task), which is used to instruct the sub-object corresponding to the target main object to take effect on the target sub-entity. The technical implementation process of the backend's splitting and execution of the main task can be understood as the basis for supporting "determining the target sub-entity and target main object" in S101 and the visual display in S102.

[0132] The current two-tier task model will serially split a main task into multiple subtasks, each of which is used to perform the corresponding business operation. Taking the main task of selling the main product a to store 1, store 2 and store 3 as an example, the main task can first be split into subtask 1 (i.e. selling the main product a to store 1), then split into subtask 2 (i.e. selling the main product a to store 2), and then split into subtask 3 (i.e. selling the main product a to store 3). Finally, subtask 1, subtask 2 and subtask 3 perform specific product distribution actions, so that store 1, store 2 and store 3 respectively have sub-product a1, sub-product a2 and sub-product a3 corresponding to the main product a. It can be seen that the biggest influencing factor for the time consumption of the main task is the splitting of the main task. In the two-tier task model, the main task is serially split into multiple subtasks. The more subtasks that need to be split, the longer it takes, which makes the overall time consumption of the main task longer. Based on this, in order to improve the processing efficiency of the main task, the embodiment of the present disclosure proposes a strategy for executing the main task based on a three-tier or more task model. It should be noted that no matter how many layers the task model has, the leaf nodes of the last layer are the ones that actually perform business operations.

[0133] Taking the four-tier task model as an example, the process of splitting the first main task can include: first, aggregating the main products of the first main task to obtain the second-tier subtasks; then, processing the second-tier subtasks according to the main products and stores to obtain the third-tier subtasks; and then, for the third-tier subtasks, according to the sub-products to be released at the right time, obtaining the fourth-tier subtasks. The fourth-tier tasks are used to execute the corresponding business operations. Whether it is the main product or the store, because they are decoupled, each layer of task splitting can be executed in parallel, which can effectively improve the efficiency of main task splitting and thus the efficiency of main task execution.

[0134] Taking Figure 5 as an example, main task 1 can be split into subtasks 11 to 15 based on the aggregation results of the main product; subtasks 11 to 14 are split based on the main product + store, resulting in {subtask 211 and subtask 212}, subtask 221, subtask 231, and {subtask 241 and subtask 242}, respectively; subtasks 211, 212, 221, and 231 are split based on the sub-product, resulting in subtask 341, subtask 342, subtask 343, and subtask 344, respectively. Among them, the subtasks responsible for executing business operations may include: subtask 15, subtask 241, subtask 242, subtask 341, subtask 342, subtask 343, and subtask 344. Compared to the two-tier task model, the time spent executing the main task is significantly reduced, and the more main products and stores involved in the batch distribution, the more significant this effect is.

[0135] In addition, considering that after multiple subtasks are completed, transactions are started immediately to update the status of the upper-level task (i.e., the main task) (the completion of subtasks can be understood by counting). In some cases, a large number of subtasks will update the status of the same main task in a short period of time, and since only one transaction can actually update the status of the main task at the same time, other transactions can only wait, which will cause problems such as excessive number of hot row writes and database connections. Based on this, in the embodiment of the present disclosure, in order to improve the above-mentioned problem when updating the status of the main task, an implementation method of timed retracement of the main task is proposed to update the status of the main task, that is, the main task periodically checks and records the status of the subtasks completed within the cycle (such as the number of subtasks that have been successfully executed, the number of subtasks that have failed to execute, etc.), without the need for subtasks to update the status of the main task one by one.

[0136] Corresponding to the method shown in Figure 1, after generating the first main task in response to the first configuration operation, the method may also include: based on a three-level or above task model, splitting the first main task into N subtasks, each of the N subtasks is used to indicate that a target sub-object corresponding to the target main object is effective in the corresponding target sub-entity, and N is equal to the number of target sub-entities; when the execution time of the first main task reaches a preset period, the execution status of the N subtasks is counted to update the status of the first main task.

[0137] It can be seen that, through S101, the target main object to be spread and the target sub-entity to be spread are determined, and data support is provided for batch spreading.

[0138] S102: Displaying the target sub-objects corresponding to the target main object in the target sub-entity on the management page of each target sub-entity, wherein the target sub-objects have the same attribute information as the corresponding target main object.

[0139] In the disclosed embodiment, the target main object and target sub-entities are determined based on the first configuration operation. Subsequently, the first batch tool can store the target sub-objects corresponding to the target main object in each target sub-entity into the corresponding target sub-entity. In this way, users can now see the target sub-objects of the stored items on the management page of each stored target sub-entity. This eliminates the need for users to manually store items one by one, greatly improving the efficiency of storage.

[0140] In some possible implementations, if the function of setting the price and inventory of sub-objects is not provided in the above-mentioned first batch tool, or the user does not use the function of setting the price and inventory of sub-objects provided in the first batch tool, then, in order to enable the sub-objects of batch products to be put on the shelves, the embodiment of the present disclosure also provides a second batch tool corresponding to batch modification. Specifically, the method may also include: S103, in response to the second configuration operation on the second batch tool on the management page of the target entity, determining the identifier of the object to be modified and the attribute information to be modified; S104, on the management page of the target entity, displaying the attribute information of the object to be modified after modification based on the attribute information to be modified. The attribute information to be modified may include at least one of the following information: title, price or inventory, and the object to be modified includes the main object and / or sub-objects.

[0141] As an example, the second batch tool on the management page of the target entity may include at least one of the following controls: a sixth control for triggering the configuration of the attribute information to be modified, the object type to be modified and the scope of the object to be modified, a seventh control for triggering the download of the template file and an eighth control for triggering the upload of the template file. S103 may, for example, include: in response to operating the sixth control, displaying the third template file; in response to operating the seventh control, downloading the third template file; in response to operating the eighth control, obtaining the fourth template file, which is the file after filling in the identifier of the object to be modified and the value of the attribute information to be modified in the third template file; then, according to the fourth template file, determining the identifier of the object to be modified and the attribute information to be modified.

[0142] As an example, S104 may include: Case 1, if the type of the object to be modified is a main object, then on the management page of the target entity, the attribute information of the main object to be modified is displayed as the attribute information modified based on the attribute information to be modified, and on the management page of the sub-entity belonging to the target entity, the attribute information of the sub-object of the main object to be modified in the sub-entity is displayed as the attribute information modified based on the attribute information to be modified; Case 2, if the type of the object to be modified is a sub-object, and the attribute information to be modified is inventory (or price), then on the management page of the sub-entity belonging to the target entity, the inventory (or price) of the sub-object of the main object to be modified in the sub-entity is displayed as the inventory (or price) modified based on the attribute information to be modified. In Case 1, the attribute information to be modified may be any one or more of title, price, and inventory.

[0143] For example, referring to FIG6 , the second batch tool is a tool corresponding to batch modification, the object is a commodity, the main object is the main commodity, and the child entity is a store. When the staff of the headquarters or management unit store of the target entity logs in to the instant retail work website, the management page is shown in the upper left corner of FIG6 . The batch tools under the commodity management item may include a tool corresponding to batch modification. It should be noted that for stores with permission to perform batch modification, the staff of the store can also log in to the instant retail work website and use the tool corresponding to the batch modification to perform batch modification work within the scope of permission. When the user clicks the "Batch Modify" button, the management page is shown in the upper right corner of FIG6 . The user can first configure the configuration items to be modified to obtain the specific template file (i.e., the third template file) that needs to be downloaded, and then obtain the fourth template file by downloading the specific template file and filling in the attribute information to be modified and the object to be modified; then, upload the fourth template file on the page shown in the lower right corner of FIG6 and click the "Submit Batch Modification" button so that the tool corresponding to the batch modification can perform batch modification based on the content of the fourth template file. Among them, the operation of the user configuring the configuration item that needs to be modified on the page shown in the upper right corner of Figure 6 corresponds to the part of the operation of the sixth control in the second configuration operation, the operation of the user clicking the "Template Download" button on the page shown in the upper right corner of Figure 6 corresponds to the part of the operation of the seventh control in the second configuration operation, and the operation of the user adding the fourth template file and clicking the "Upload Template" button on the page shown in the lower right corner of Figure 6 corresponds to the part of the operation of the eighth control in the second configuration operation.

[0144] For tools corresponding to batch modification, in order to guide users to use the tool, the usage process of the tool can be displayed, and the corresponding copy can be "1. Download the template; 2. Fill in the content; 3. Upload the file; 4. Submit the modification."

[0145] When downloading a modification template, the attributes to be modified include price, title, and inventory, of which only one option can be selected. The object type to be modified includes main products and sub-products, of which only one can be selected. Furthermore, since the titles of the main and sub-products cannot be differentiated, modifying the main product title also modifies the sub-product titles. Therefore, when "Title" is selected for modification, the product type selection is hidden, and a prompt can be added: "Only the main product title can be modified. Modifying the main product title will also modify the sub-products in all stores associated with the main product." There are three ways to configure the scope of the object to be modified. For details, see the description of the three methods for selecting the main object in the example shown in FIG2 in S101 above. After completing the configuration of the above three contents, you can determine the only modification template (i.e., the third template file). Click "Download Template" below, and a pop-up window will pop up. The title of the pop-up window can be "Download Result", and the text of the pop-up window can be "The task of downloading the template has been submitted successfully. Due to the large amount of data, it takes a certain amount of execution time. Closing this page will not terminate the download operation. You can view the operation results in [Batch Operation Record] later". The operation items of the pop-up window can include "View Batch Operation Record" and "Close". If you click "View Batch Operation Record", you will jump to the page corresponding to [Batch Operation Record]. If you click "Close", you will return to the first step of the page corresponding to the batch modification, such as the initial state of the batch modification shown in the upper right corner of Figure 6.

[0146] When the object type to be modified is the main product, the implementation process may include: a) Main product ID, which is required and can be viewed and copied in the reference information; b) Specification ID, (1) required when the modification content is "price" or "inventory". When there are multiple specifications of a product, if all specifications need to be modified, fill in "all / all". If some specifications need to be modified, only the specification ID to be modified needs to be filled in. If it is not filled in or filled in incorrectly, the specification will not be modified. (2) When the modification content is "title", since multiple specifications of a product can only correspond to one title, there is no field column for specification ID; c) Store ID, which is required. Filling in "all / all" will select all stores. When selecting some stores, all store IDs can be filled in this field, separated by ";". If it is not filled in, it will be skipped and not modified; d) Price, this column is only available when the modification content is "price". It is required. The unit can be RMB, and it is accurate to 0.01 at most. If it is not filled in, it will not be modified, and the processing will fail and an error will be reported. If If the store has no sub-products, skip the process; e) Inventory. This column is only available when the modification content is "Inventory". It is required and the value must be an integer greater than or equal to 1. The upper limit can be 999999. If it is not filled in, the modification will not be made, the processing will fail and an error will be reported. If the store has no sub-products, skip the process; f) Title. This column is only available when the modification content is "Title". It is required. If it is not filled in, the modification will not be made, the processing will fail and an error will be reported. g) Whether it affects sub-products at the same time. When the modification content is "Title", this column is not available. When the modification content is "Price" or "Inventory", this column is displayed. When this column is "Yes", the price and inventory of all related sub-products are also modified. When this column is "No", only the main product is modified and the store sub-products are not modified.

[0147] When the object type to be modified is a sub-product, the implementation process may include: a) Specification ID, which is required. When a sub-product has multiple specifications, if all specifications need to be modified, fill in "all". If some specifications need to be modified, only the specification ID to be modified needs to be filled in. If it is not filled in or filled in incorrectly, the specification will not be modified; b) Store ID, which is required. Filling in "all" will select all stores. When selecting some stores, all store IDs can be filled in this field, separated by ";". If it is not filled in, the modification will be skipped; c) Price, which is only present when the modification content is "price". It is required. The unit can be yuan, with a maximum accuracy of 0.01. If it is not filled in, the modification will not be made, the processing will fail and an error will be reported. If the store has no sub-products, the modification will be skipped; d) Inventory, which is only present when the modification content is "inventory". It is required. The value must be an integer greater than or equal to 1, with an upper limit of 999999. If it is not filled in, the modification will not be made, the processing will fail and an error will be reported. If the store has no sub-products, the modification will be skipped.

[0148] When uploading a modification template, you can also configure the modification content, for example, it can include: modified attribute information and modification object type. The optional items of the attribute information to be modified may include: price, title and inventory, and only one optional item can be selected; the optional items of the object type to be modified may include: main product and sub-product, and only one optional item can be selected. Moreover, since the title information of the main and sub-products cannot be differentiated, when the title information of the main product is modified, the title information of the sub-product will be modified at the same time. Therefore, when the content to be modified is selected as "Title", the product type selection is hidden, and a prompt copy can be added: "Only the title of the main product can be modified. After the main product title is modified, the sub-products of all stores associated with the main product will be modified at the same time." After configuring the above two contents, you can upload the fourth template file. The text included in the uploaded dotted box can be "Please download the template first, and fill in the downloaded template according to the requirements before uploading. A maximum of 100,000 rows can be uploaded at a time, and the excess will fail to process. If the quantity limit is exceeded, it can be imported in batches." After uploading the fourth template file, the verification performed may include: file format verification and template header verification. The file formats supported for upload may include Excel files. The template header verification can be understood as: based on the selected modified attribute information and modified object type, determine the file header format that needs to be verified. When the format does not match, the upload fails, and the prompt "Word is missing, please re-download the template to check the correct format" is displayed. When the fourth template file passes the inspection, you can click "Submit Batch Modification" at the bottom. After clicking "Submit Batch Modification", you can see the lower left corner of Figure 6, and the "Upload Result" will be prompted through a pop-up window or other means. The text of the pop-up window can be "Batch modification submitted successfully. Due to the large amount of data, it takes a certain amount of execution time. Closing this page will not terminate the batch modification operation. You can view the operation results in [Batch Operation Record] later." The operation items of the pop-up window can include "View Batch Operation Record" and "Close". If you click "View Batch Operation Record", you will jump to the page corresponding to [Batch Operation Record]. If you click "Close", you will return to the first step of the page corresponding to the batch modification, such as the initial state of the batch modification shown in the upper right corner of Figure 6.

[0149] When the modification object type is a sub-product, the export failure processing may include: the import upper limit can be set to 50,000, the excess will not be processed, and the export failure will be directly confirmed. The error text may be: The upper limit of the number of stores set at a single time has been exceeded, please re-upload. In order for the user to be able to modify and import directly after exporting, the failure reason needs to be pointed out in the error report, so that the user can make modifications according to the failure reason. In the file imported by the merchant, a failure record table is added, and after downloading, the table is selected by default. In the embodiment of the present disclosure, failure records can be generated by type.

[0150] When the modified object type is the main product, if the modified attribute information is the title, the modification of the main product will be synchronized to the sub-product by default, so the result can only show the modification results of the main product. If the modified attribute information is the price, the modification errors of the main product and the sub-product are output at the same time; all modification contents are flattened (that is, a single record is at the granularity of "main product ID SKU ID and store ID", where the SKU ID is the content of the SKU ID column filled in by the user), or it can also be understood as only flattening the store; the field descriptions for the downloaded results are: 1) main product ID, 2) specification ID, 3) object type (main product or sub-product), 4) store ID (when the object type is "main product", the store ID column is "-", when the object type is "sub-product", the store ID column is the corresponding store ID), 5) price (the price initially filled in by the user), 6) result (can be failure), and 7) reason (used to display the reason for failure). If the modified attribute information is inventory, the main product modification error and the sub-product modification error are output at the same time; all modification contents are flattened (that is, a single record is at the granularity of "main product ID SKU ID and store ID", where SKU ID is the content of the SKU ID column filled in by the user), or it can also be understood as only flattening the store; the field descriptions for the downloaded results are: 1) main product ID, 2) specification ID, 3) object type (main product or sub-product), 4) store ID (when the object type is "main product", the store ID column is "-", when the object type is "sub-product", the store ID column is the corresponding store ID), 5) inventory (the inventory initially filled in by the user), 6) result (can be failure), and 7) reason (used to display the reason for failure).

[0151] After executing S101 to S104 , the target sub-entity can perform operations such as listing, delisting, and deleting its own target sub-object.

[0152] In some possible implementations, chain enterprises are worried that some stores will modify the commodity attribute information of the sub-commodities they sell. Therefore, there is a need to batch export the commodity attribute information of the sub-commodities corresponding to the main commodities they are concerned about in some stores to verify the commodity attribute information (especially price and inventory). Therefore, the batch tool provided by the embodiment of the present disclosure can also include a batch export corresponding tool (i.e., a third batch tool). Specifically, the embodiment of the present disclosure can also include: first, in response to the third configuration operation on the third batch tool on the management page of the target entity, the export progress of the corresponding export task is displayed on the batch operation record page; then, in response to the completion of the export task for the object to be exported, the batch operation record page displays a ninth control for triggering the download of the result of the export task; then, in response to operating the ninth control, the export file corresponding to the export task is downloaded, and the export file includes the value of the preset export field of each object to be exported. In this way, through the batch export tool, it is convenient for users to quickly obtain the commodity attribute information corresponding to at least one main commodity in multiple stores they are concerned about. It should be noted that the batch export corresponding tool can be used by the headquarters, management unit store or authorized store.

[0153] As an example, the third batch tool on the management page of the target entity may include at least one of the following controls: a tenth control for triggering the selection of the main object to be exported, an eleventh control for triggering the batch export configuration, a twelfth control for triggering the selection of the type of object to be exported, and a thirteenth control for triggering the export. Then, the third configuration operation may include operating the tenth control to select the main object to be exported, operating the eleventh control, operating the twelfth control to select the type of object to be exported, and operating the thirteenth control to trigger the export task.

[0154] Among them, the corresponding tool for batch export can first select a main product, and then export the main product or the sub-products of the main product in all stores; or, it can also first select multiple main products, and then export these main products or the sub-products corresponding to these main products in all stores.

[0155] For example, as shown in Figure 7, in the tool corresponding to batch export, multiple filtered main products can be displayed by filtering at least one of the conditions of product price range, product type or product sales volume. Each main product corresponds to a multiple-choice box and can be checked as a target for batch export; the "Export sub-products" option can also be included in the drop-down menu of "Sub-product batch operation"; each main product operation item can also correspond to a separate "Export all sub-products" option; users can click the above "Export sub-products" or "Export all sub-products" option to realize the batch export of sub-products corresponding to the selected main product. After clicking the "Export sub-products" or "Export all sub-products" option, the page corresponding to the batch export of products can be displayed through a drawer or other means. On this page, you can select the export product type and display report fields. Among them, the export product type includes two radio buttons "Export only the main product" and "Export the main product and all store sub-products under the product". It should be noted that you can set an upper limit for the number of main products that can be selected for a single batch export, such as 10. In this case, a prompt can be displayed at the top of the page corresponding to the batch exported products. The text can be "To ensure that the export results can be opened and used normally, the batch export sub-product function supports the selection of up to 10 main products." The rightmost side of the prompt will display the ratio of the currently selected main products, such as 1 / 10. The font or background color of the prompt can be used to distinguish whether the selected main products exceed the preset upper limit. For example, if it does not exceed the upper limit, the font will be green, and if it does, the font will be red.

[0156] For batch export, the attribute information of the exported sub-products can be pre-set according to the needs. For example, the attribute information of the exported sub-products may include: sub-product ID, sub-product name, first-level category, second-level category, third-level category, fourth-level category, sub-product type, sub-product code, specification ID (or SKU ID), sub-product specification, sub-product delivery time, sub-product price, regional inventory, sales volume, sub-product review status, sub-product link and product number. It may also include: store ID, main product ID or main product status. It should be noted that the main product information needs to be exported at the same time, and the main product and sub-product types must be marked. If the store ID corresponding to the main product is available, "None" can be filled in. The export quantity shall not exceed 200,000. If it exceeds 200,000, the export will fail and the prompt "The number of sub-products exceeds 200,000 and export is not supported. Please contact customer service for processing" will be displayed. If some fields in the sub-product information are empty, it will not affect the entire export task. There is no need to distinguish between the main and sub-products in different tables. They can be exported in the same table.

[0157] For the export entry, each main product includes an "Export all sub-products" option. Clicking this will prompt a confirmation pop-up window. Clicking "OK" in the pop-up window triggers the export task. If you select "Export the main product and all its store sub-products," the main product and all its sub-products will be exported. If you switch the export type to "Export only the main product," only the main product information will be exported. The report field must list all export fields. Optionally, the number of main products currently being exported can be displayed at the bottom.

[0158] After triggering an export task, a prompt will appear: "Export started. Please check the export results later on the bulk operation log page." If the export quantity exceeds the set limit, a failure message will be added to the corresponding row of the batch export task on the corresponding page to alert the user. For example, a batch export task exceeding 200,000 items will be marked as failed. The failure reason could be "Partial failure, exceeding the 200,000 limit," the failure message could be "Exceeded limit," and the message could be "The number of exported items has exceeded the 200,000 limit. Export of the excess items failed. Please verify and export separately." For batch export tasks, a record function for "Export all sub-items" will be added to the corresponding page of the batch operation log. The operation status can include: task in progress (with the message "in progress"), task completed (with the message "completed"), and task failed (with the message "processing failed"). If the operation is successful, a function will be added to download the export results, allowing users to directly download the batch exported file. If the operation fails, users can retry and re-export the sub-items, but the retry will be generated for a new export task. It should be noted that if there is an export task in progress, a new export task cannot be initiated and a prompt will be displayed: "There is already an export task in progress. Please try again after it is completed. You can check whether the ongoing export task has been completed on the corresponding page of the batch operation record." For user convenience, you can also add a new export record in the "Historical Report" of the export record. If the export is successful, you can directly click "Download". If it fails, you can directly click "Retry".

[0159] The above description applies to the case where "Export all sub-items" is selected for a single main item. If "Export sub-items" is selected for multiple main items, when the "Export main item and all store sub-items under it" option is selected, an upper limit on the number of main items that can be selected can be set. For example, you can only support exporting sub-items for 10 main items. If more than 10 main items are selected, the "Export" button will be disabled. When the "Export only main items" option is selected, there is no limit on the number of main items that can be selected. The export results can be viewed on the page corresponding to the batch operation record.

[0160] In some possible implementations, the batch tool provided by the embodiments of the present disclosure may further include a batch operation recording tool. Specifically, the batch operation recording page corresponding to the batch operation recording tool may include at least one of the following contents: batch operation personnel, details of the batch operation, the number of main objects involved in the batch operation, or the number of sub-objects involved in the batch operation. The batch operation recording tool supports viewing each batch operation, for example, you can refer to the operation status of each batch operation (such as in operation, successful operation, failed operation, etc.). In addition, it can also display the details of the batch operation (such as successful product details, failed product details, etc.), and guide subsequent actions (such as guiding the distribution of products for successfully released products, guiding the viewing of reasons for failed product releases, and guiding the modification and supplement of information for products stored in the draft box, etc.).

[0161] It should be noted that for batch operation records, each action can be a record. For example, if 10 main products are selected for listing at the same time, only one corresponding record will be retained.

[0162] As an example, the content recorded in the bulk operation record may include: filter items, operation columns, and bulk operation lists.

[0163] Among them, the filtering items may include the operator, that is, the account logged in when performing the operation, the organization to which the account belongs (such as the headquarters, a certain management unit store or store), or the user corresponding to the account.

[0164] In the Operation column, you can add "Batch Operation Details" to record all user information that may be used for subsequent statistics, analysis, verification, and other purposes for each batch operation. The details of each batch operation are described for each type of batch operation. For batch creation, the details of the batch operation can include: a) Operation type, which can be batch creation; b) Operation time, which can be accurate to the second, such as "2023-11-12 22:59:33"; c) Operator; d) Uploaded attachments, which can record the name of the uploaded attachment. Downloading uploaded attachments is not supported. For batch product distribution (including the one-click configuration of a single main product to all stores, the new store function and the batch product distribution function), the details of the batch operation can be recorded specifically: a) Operation type, which can be batch product distribution; b) Operation time; c) Operator; d) Selected products, which can display a list of products (such as product name, product ID, price, release date, etc.); e) Selected store, which can display a list of stores (such as store name, store ID, etc.); f) Price and inventory, which can record the options during batch operation. If "Consistent with the main product" is selected, "Consistent with the main product" will be displayed. If "Custom input" is selected, the custom input value will be displayed. For batch listings, the details of the batch operation can specifically record: a) Operation type, which can be batch listing; b) Operation time, which can be accurate to the second, such as "2023-11-12 22:59:33"; c) Operator; d) Operation scope, which can be displayed according to the selection made during the batch operation. If "List main product and sub-products at the same time" is selected, "List main product and sub-products at the same time" will be displayed; if "List only main product" is selected, "List only main product" will be displayed; e) Selected products, which can display a list of products (such as product name, product ID, price, release date, etc.). For batch delisting, the details of the batch operation can specifically record: a) Operation type, which can be batch delisting; b) Operation time, which can be accurate to the second, such as "2023-11-12 22:59:33"; c) Operator; d) Selected products, which can display a list of products (such as product name, product ID, price, release date, etc.). For batch deletion, the details of the batch operation can specifically record: a) Operation type, which can be batch deletion; b) Operation time, which can be accurate to the second, such as "2023-11-12 22:59:33"; c) Operator; d) Selected products, which can display a list of products (such as product name, product ID, price, release date, etc.). For batch modification, the details of the batch operation can specifically record: a) Operation type, which can be batch modification; b) Operation time, which can be accurate to the second, such as "2023-11-12 22:59:33"; c) Operator; d) Uploaded attachments, which can record the name of the uploaded attachment. Downloading uploaded attachments is not supported.For batch export, the details of the batch operation can be recorded specifically: a) Operation type, which can be batch export or export data; b) Operation time, which can be accurate to seconds, such as "2023-11-12 22:59:33"; c) Operator; d) Export scope, which can be displayed according to the selection made during batch export. If "Export only main product" is selected, "Export only main product" will be displayed; if "Export main product and all store sub-products under this product" is selected, "Export main product and all store sub-products under this product" will be displayed.

[0165] In the batch operation list, you can add the "Main Product Quantity" column and the "Sub-Product Quantity" column. For different types of batch operations, the specific contents of the batch operation list are introduced. For batch creation, the main product-related content can include: a) Total, used to record the number of main products involved in this operation; b) Success, used to record the number of successful main products. You can click "View" to jump to the Sales tab of the management page. By default, the successfully created main products are filtered out. Click "Reset" to uncheck them; c) Draft box, used to record batch operations that failed to create orders and saved them in the draft box. You can click "View" to jump to the draft box page. By default, these products are filtered out. Click "Reset" to uncheck them; d) Failure, used to record the number of main products that failed to be created. Since batch creation does not involve the operation of sub-products, sub-products can be displayed as "-". Since batch creation does not involve the operation of main products, the main products can be displayed as "-". For batch products, the content related to sub-products can include: a) Total, used to record the number of sub-products involved in this operation; b) Success, used to record the number of sub-products successfully placed; c) Draft box, since there is no process of putting products into the draft box, it can be displayed as "-"; d) Failure, used to record the number of sub-products that failed to be placed. For batch shelving, the content related to the main product can include: a) Total, used to record the number of main products that need to be put on the shelves this time; b) Success, used to record the number of main products that have been successfully put on the shelves. You can click "View" to jump to the Sales tab of the management page. By default, the main products that have been successfully put on the shelves are filtered out. Click "Reset" to uncheck them; c) Draft box, since there is no process of putting products into the draft box for batch shelving, it can be displayed as "-"; d) Failure, used to record the number of main products that have failed to be put on the shelves. For batch listing, the content related to sub-items may include: a) Total, used to record the number of sub-items that need to be listed this time; b) Success, used to record the number of sub-items that have been successfully listed; c) Draft box, since there is no process of putting items into the draft box for batch listing, it can be displayed as "-"; d) Failure, used to record the number of sub-items that failed to be listed. For batch delisting, the content related to main items may include: a) Total, used to record the number of main items that need to be delisted this time; b) Success, used to record the number of main items that have been successfully delisted. You can click "View" to jump to the Sales tab of the management page. By default, the main items that have been successfully delisted are filtered out. Click "Reset" to uncheck the selection; c) Draft box, since there is no process of putting items into the draft box for batch delisting, it can be displayed as "-"; d) Failure, used to record the number of main items that failed to be delisted.For batch delisting, the content related to sub-items may include: a) Total, used to record the number of sub-items that need to be delisted this time; b) Success, used to record the number of sub-items that have been successfully delisted; c) Draft Box, since there is no process of putting items into the draft box for batch delisting, it can be displayed as "-"; d) Failure, used to record the number of sub-items that failed to be delisted. For batch deletion, the content related to the main item may include: a) Total, used to record the number of main items that need to be deleted this time; b) Success, used to record the number of main items that have been successfully deleted. You can click "View" to jump to the Sales tab of the management page. By default, the main items that have been successfully deleted are filtered out. Click "Reset" to uncheck the selection; c) Draft Box, since there is no process of putting items into the draft box for batch deletion, it can be displayed as "-"; d) Failure, used to record the number of main items that failed to be deleted. For batch deletion, the sub-items related content may include: a) Total, used to record the number of sub-items that need to be deleted this time; b) Success, used to record the number of sub-items successfully deleted; c) Draft box, because there is no process of putting into the draft box for batch deletion, it can be displayed as "-"; d) Failure, used to record the number of sub-items that failed to be deleted. For batch modification, when the scope of batch modification of products is selected as "Modify only the main product" or "Modify the main product and act on all sub-items at the same time", the modification quantity is displayed. When "Modify sub-items" is selected, the main product can be displayed as "-" accordingly; when the scope of batch modification of products is selected as "Modify the main product and act on all sub-items at the same time" or "Modify sub-items", the modification quantity is displayed. When "Modify only the main product" is selected, the sub-items can be displayed as "-". Specifically, for batch modification, the content related to the main product may include: a) Total, used to record the number of main products that need to be modified this time; b) Success, used to record the number of main products that have been successfully modified. It supports clicking "View" to jump to the Sales tab of the management page. By default, the main products that have been successfully modified are filtered out and can be unchecked after clicking "Reset"; c) Draft box, used to record batch operations of failed modifications that are saved to the draft box. It supports clicking "View" to jump to the draft box page. By default, these products are filtered out and can be unchecked after clicking "Reset". If only the price or inventory is modified, there will be no step of putting them into the draft box, so it can be displayed as 0; d) Failure, used to record the number of main products that failed to be modified. For batch modification, the content related to sub-products may include: a) Total, used to record the number of sub-products that need to be modified this time; b) Success, used to record the number of sub-products that have been successfully modified; c) Draft box. Since there is no step of putting them into the draft box for batch modification of sub-products, it can be displayed as "-"; d) Failure, used to record the number of sub-products that failed to be modified. For batch export, since there is no change to product information, status, etc. in the exported quantity, the corresponding main product and sub-product columns can be displayed as "-".

[0166] In addition, the batch tools provided in the embodiments of the present disclosure may further include at least one of the following tools: a batch listing tool, a batch delisting tool, or a batch deletion tool.

[0167] For the above-mentioned batch listing tool, you can list multiple main products in batches, or you can list sub-products corresponding to one or more main products at the same time. The specific operations may include: checking the main product -> batch listing -> selecting to list the main product and sub-products at the same time -> pop-up window confirmation. Alternatively, you can also list only the sub-products corresponding to these main products in batches when the main product has been listed. For example, the main product is successfully listed, but the corresponding sub-products fail to be listed. Therefore, a separate operation will be required to "list all sub-products". The specific operations may include: checking the main product -> batch operation of sub-products -> batch listing -> select the store to list in the drawer > click confirm. Alternatively, you can only list multiple main products in batches, and not list the sub-products. Alternatively, you can list multiple main products in batches, but only list the corresponding sub-products in some stores. In the case of successful batch listing, the sub-products are sold normally; in the case of failed batch listing, the user can download the reason for failure (such as abnormal store status) and re-list after resolving the reason for failure.

[0168] For the above-mentioned batch delisting tool, multiple main products can be delisted in batches, and all corresponding sub-products will also be delisted at the same time. Specific operations may include: checking the main product -> batch operation of main products -> batch delisting -> pop-up window confirmation. Alternatively, you can also batch delist the sub-products corresponding to multiple main products in some stores (for example, due to supply chain problems in certain regions, the sub-products of stores in that region will be temporarily delisted, and may be put back on the shelves later). Specific operations may include: checking the main product -> batch operation of sub-products -> batch delisting -> select the store to be delisted in the drawer -> click confirm. For successful batch delisting, there are no other operations. For failed batch delisting, users can download the failure reasons and remove the products again after resolving the failure reasons.

[0169] For the above-mentioned batch deletion tool, you can batch delete multiple main products, and all corresponding sub-products will be deleted at the same time. Specific operations may include: check the main product -> batch operation of main products -> batch deletion -> pop-up window confirmation. Alternatively, you can batch delete the sub-products corresponding to multiple main products in some stores (for example, due to supply chain problems in certain regions, the product is no longer sold and is directly deleted, that is, the sub-products corresponding to the main product are cancelled in the store). Specific operations may include: check the main product -> batch operation of sub-products -> batch deletion -> select the deleted store in the drawer -> click confirm. For successful batch deletion, there are no other operations. For failed batch deletion, users can download the failure reason and delete again after resolving the failure reason.

[0170] As shown in Figure 8, the batch tools developed on the management page of the embodiment of the present disclosure may include at least: batch product distribution, batch modification, batch listing, batch delisting, batch deletion, batch export and batch operation records, so as to provide users with the convenience of batch management of goods on the online sales platform in the instant retail scenario (especially in the instant retail scenario where a large number of large chain enterprises are settled), thereby greatly improving the efficiency of users' batch management of goods, and also improving the user experience of using the work website with the management page.

[0171] It can be seen that through this method, for a target entity belonging to a chain entity, when there is a need to batch add sub-objects corresponding to the main object to certain target sub-entities in the target entity, a first batch tool is provided on the management page of the target entity, and the user only needs to perform a first configuration operation on the first batch tool to quickly realize the need, that is, the user uses the first batch tool once, and based on the target sub-entities and target main objects determined by using the first batch tool this time, batch operates the target sub-objects corresponding to the target main object in the target sub-entity, so that the target sub-objects belonging to the target sub-entity and corresponding to the target main object are displayed on the management page of each target sub-entity, and the user does not need to operate the target main object and the target sub-object one by one based on the identification of different objects in the chain entity, which overcomes the current problem of poor processing efficiency caused by the inability to batch process objects in the chain entity, improves the processing efficiency of objects in the chain entity, and thus brings convenience to the staff of the chain entity in the instant retail scenario.

[0172] Accordingly, the embodiment of the present disclosure further provides a batch processing device 900, as shown in FIG9 . The device 900 may include:

[0173] A first determining unit 901 is configured to determine target sub-entities and target primary objects in response to a first configuration operation on a first batch tool on a management page of a target entity, wherein the target sub-entities are subordinate entities of the target entity, and the target primary objects are objects within the target entity. The first batch tool is configured to batch-set primary objects within an entity to sub-entities.

[0174] The first display unit 902 is configured to display, on the management page of each target sub-entity, a target sub-object corresponding to the target main object in the target sub-entity, wherein the target sub-object has the same attribute information as the corresponding target main object.

[0175] In a possible implementation, the first batch tool on the management page of the target entity includes a first control for triggering selection of a main object and a second control for triggering selection of a sub-entity, and the first configuration operation includes operating the first control corresponding to the target main object to select the target main object and operating the second control corresponding to the target sub-entity to select the target sub-entity;

[0176] and / or, the first batch tool on the management page of the target entity includes a first control for triggering selection of a main object and a third control for triggering application to all sub-entities, the first configuration operation includes operating the first control corresponding to the target main object to select the target main object and operating the third control to apply to all sub-entities of the target entity, the target sub-entities being all sub-entities included in the target entity;

[0177] And / or, the first batch tool on the management page of the target entity includes a fourth control for triggering the download of a template file and a fifth control for triggering the upload of a template file, the first configuration operation includes operating the fourth control to obtain a first template file and operating the fifth control to upload a second template file, the second template file being the file after the identifier of the target main object and the identifier of the target sub-entity are filled in the first template file.

[0178] In a possible implementation, the first determining unit 901 is specifically configured to:

[0179] In response to the first configuration operation, a first main task is generated, where the first main task is used to instruct to make the sub-object corresponding to the target main object effective on the target sub-entity;

[0180] The apparatus 900 further includes:

[0181] a splitting unit, configured to split the first main task into N subtasks based on a three-level or higher-level task model, wherein each of the N subtasks is configured to indicate that a target subobject corresponding to the target main object is effective in a corresponding target subentity, where N is equal to the number of the target subentities;

[0182] The statistics unit is used to count the execution status of the N subtasks when the execution time of the first main task reaches a preset period.

[0183] In a possible implementation, the apparatus 900 further includes:

[0184] a second determining unit, configured to determine, in response to a second configuration operation on a second batch tool on the management page of the target entity, an identifier of an object to be modified and attribute information to be modified, wherein the attribute information to be modified includes at least one of the following information: title, price, or inventory, and the object to be modified includes a main object and / or a sub-object;

[0185] The second display unit is configured to display, on the management page of the target entity, the attribute information of the object to be modified after being modified based on the attribute information to be modified.

[0186] In one possible implementation, the second batch tool on the management page of the target entity includes at least one of the following controls: a sixth control for triggering configuration of attribute information to be modified, an object type to be modified, and an object range to be modified; a seventh control for triggering downloading of a template file; and an eighth control for triggering uploading of a template file. The second determining unit is specifically configured to:

[0187] In response to operating the sixth control, displaying a third template file;

[0188] In response to operating the seventh control, downloading the third template file;

[0189] In response to operating the eighth control, the fourth template file is obtained, wherein the fourth template file is a file obtained by filling in the identifier of the object to be modified and the value of the attribute information to be modified in the third template file;

[0190] According to the fourth template file, the identifier of the object to be modified and the attribute information to be modified are determined.

[0191] In a possible implementation, the second display unit is specifically configured to:

[0192] If the type of the object to be modified is a main object, then on the management page of the target entity, the attribute information of the main object to be modified is displayed as the attribute information modified based on the attribute information to be modified; and on the management page of a child entity belonging to the target entity, the attribute information of the child object of the main object to be modified in the child entity is displayed as the attribute information modified based on the attribute information to be modified;

[0193] If the type of the object to be modified is a sub-object, and the attribute information to be modified is inventory or price, then on the management page of the sub-entity belonging to the target entity, the price or inventory of the sub-object of the main object to be modified in the sub-entity is displayed as the price or inventory modified based on the attribute information to be modified.

[0194] In a possible implementation, the apparatus 900 further includes:

[0195] a third display unit, configured to display, in response to a third configuration operation on a third batch tool on the management page of the target entity, an export progress of the corresponding export task on a batch operation record page;

[0196] a fourth display unit, configured to display a ninth control for downloading a result of the export task on the batch operation record page in response to completion of the export task for the object to be exported;

[0197] A downloading unit is used to download an export file corresponding to the export task in response to operating the ninth control, wherein the export file includes a value of a preset export field of each object to be exported.

[0198] In one possible implementation, the third batch tool on the management page of the target entity includes at least one of the following controls: a tenth control for triggering selection of a primary object to be exported, an eleventh control for triggering batch export configuration, a twelfth control for triggering selection of a type of object to be exported, and a thirteenth control for triggering export, and the third configuration operation includes operating the tenth control to select the primary object to be exported, operating the eleventh control, operating the twelfth control to select the type of object to be exported, and operating the thirteenth control to trigger the export task.

[0199] In one possible implementation,

[0200] The management page of the target entity also includes a batch operation record tool, and the batch operation record page corresponding to the batch operation record tool includes at least one of the following contents: batch operation personnel, details of the batch operation, the number of main objects involved in the batch operation, or the number of sub-objects involved in the batch operation.

[0201] In one possible implementation,

[0202] The management page of the target entity also includes at least one of the following tools: a batch listing tool, a batch delisting tool, or a batch deletion tool.

[0203] It should be noted that the specific implementation of the device 900 and the technical effects achieved can be found in the relevant description of the method shown in FIG1 .

[0204] In addition, an embodiment of the present disclosure also provides an electronic device, which includes a processor and a memory: the memory is used to store instructions or computer programs; the processor is used to execute the instructions or computer programs in the memory, so that the electronic device executes any implementation of the method provided in the embodiment of the present disclosure.

[0205] Referring to FIG10 , a schematic diagram of the structure of an electronic device 1000 suitable for implementing an embodiment of the present disclosure is shown. The terminal devices in the embodiments of the present disclosure may include, but are not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. The electronic device shown in FIG10 is merely an example and should not limit the functionality and scope of use of the embodiments of the present disclosure.

[0206] As shown in FIG10 , the electronic device 1000 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 1001, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage device 1008 into a random access memory (RAM) 1003. Various programs and data required for the operation of the electronic device 1000 are also stored in the RAM 1003. The processing device 1001, the ROM 1002, and the RAM 1003 are connected to each other via a bus 1004. An input / output (I / O) interface 1005 is also connected to the bus 1004.

[0207] Typically, the following devices may be connected to the I / O interface 1005: an input device 1006 including, for example, a touch screen, a touchpad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 1007 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 1008 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 may allow the electronic device 1000 to communicate with other devices wirelessly or by wire to exchange data. Although FIG. 10 illustrates the electronic device 1000 with various devices, it should be understood that not all of the devices shown are required to be implemented or present. More or fewer devices may alternatively be implemented or present.

[0208] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a non-transitory computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication device 1009, or installed from the storage device 1008, or installed from the ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment of the present disclosure are performed.

[0209] The electronic device provided by the embodiment of the present disclosure and the method provided by the above embodiment belong to the same inventive concept. For technical details not fully described in this embodiment, please refer to the above embodiment, and this embodiment has the same beneficial effects as the above embodiment.

[0210] The embodiments of the present disclosure further provide a computer-readable medium, in which instructions or computer programs are stored. When the instructions or computer programs are executed on a device, the device executes any implementation of the method provided in the embodiments of the present disclosure.

[0211] It should be noted that the computer-readable medium mentioned above in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or component, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, device, or component. In the present disclosure, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, which carries computer-readable program code. Such a propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport a program for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium may be transmitted using any suitable medium, including but not limited to wires, optical cables, RF (radio frequency), etc., or any suitable combination thereof.

[0212] In some embodiments, the client and server can communicate using any currently known or later developed network protocol, such as HTTP (Hypertext Transfer Protocol), and can be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), an internet (e.g., the Internet), and a peer-to-peer network (e.g., an ad hoc peer-to-peer network), as well as any currently known or later developed network.

[0213] The computer-readable medium may be included in the electronic device, or may exist independently without being incorporated into the electronic device.

[0214] The computer-readable medium carries one or more programs. When the one or more programs are executed by the electronic device, the electronic device can perform the method.

[0215] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages, or a combination thereof, including, but not limited to, object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on the remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., through the Internet using an Internet service provider).

[0216] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram can represent a module, program segment, or a part of code, and the module, program segment, or a part of code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order than that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of the boxes in the block diagram and / or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0217] The units involved in the embodiments described in this disclosure may be implemented in software or hardware, wherein the name of a unit / module does not, in some cases, limit the unit itself.

[0218] The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, and without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chip (SOCs), complex programmable logic devices (CPLDs), and the like.

[0219] In the context of the present disclosure, a machine-readable medium can be a tangible medium that can contain or store a program for use by or in conjunction with an instruction execution system, device or equipment. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium can include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0220] It should be noted that the various embodiments of this disclosure are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. Reference can be made to the descriptions of the systems or devices disclosed in the embodiments for similarities and differences between them. Since the systems or devices disclosed in the embodiments correspond to the methods disclosed in the embodiments, their descriptions are relatively simple, and reference can be made to the descriptions of the methods for any related details.

[0221] It should be understood that in the present disclosure, "at least one (item)" refers to one or more, and "plurality" refers to two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0222] It should also be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article, or device comprising the element.

[0223] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0224] It should be noted that in the embodiments of the present disclosure, user sensitive information is not involved, and user-related information is obtained, used and determined after user authorization. In one example, before obtaining user-related information, the corresponding interface displays prompt information related to obtaining data use authorization. This prompt information is based on relevant laws and regulations and informs the user of the type, scope of use, usage scenarios, etc. of the personal information involved in this disclosure in an appropriate manner, so that the user can determine whether to agree to the authorization based on the prompt information. It can be understood that the above-mentioned notification and the process of obtaining user authorization are only illustrative and do not constitute a limitation on the implementation method of the present disclosure. Other methods that meet relevant laws and regulations can also be applied to the implementation method of the present disclosure.

[0225] The above description of the disclosed embodiments is intended to enable one skilled in the art to implement or use the present disclosure. Various modifications to these embodiments will be readily apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure is not limited to the embodiments shown herein, but is intended to be construed in the widest manner consistent with the principles and novel features disclosed herein.

Claims

1. A batch processing method comprising: In response to a first configuration operation on a first batch tool on a management page of a target entity, target sub-entities and target primary objects are determined, wherein the target sub-entities are subordinate entities of the target entity, and the target primary objects are objects within the target entity, and the first batch tool is used to batch set primary objects within an entity to the sub-entities; On the management page of each target sub-entity, a target sub-object corresponding to the target main object in the target sub-entity is displayed, and the attribute information of the target sub-object is the same as that of the corresponding target main object.

2. The method according to claim 1, wherein The first batch tool on the management page of the target entity includes a first control for triggering selection of a main object and a second control for triggering selection of a sub-entity, and the first configuration operation includes operating the first control corresponding to the target main object to select the target main object and operating the second control corresponding to the target sub-entity to select the target sub-entity; and / or, the first batch tool on the management page of the target entity includes a first control for triggering selection of a main object and a third control for triggering application to all sub-entities, the first configuration operation includes operating the first control corresponding to the target main object to select the target main object and operating the third control to apply to all sub-entities of the target entity, the target sub-entities being all sub-entities included in the target entity; And / or, the first batch tool on the management page of the target entity includes a fourth control for triggering the download of a template file and a fifth control for triggering the upload of a template file, the first configuration operation includes operating the fourth control to obtain a first template file and operating the fifth control to upload a second template file, the second template file being the file after the identifier of the target main object and the identifier of the target sub-entity are filled in the first template file.

3. The method according to claim 1 or 2, wherein: The determining of the target sub-entity and the target main object in response to a first configuration operation on a first batch tool of a management page of the target entity includes: In response to the first configuration operation, a first main task is generated, where the first main task is used to instruct to make the sub-object corresponding to the target main object effective on the target sub-entity; The method further comprises: Based on a three-level or higher-level task model, split the first main task into N subtasks, each of the N subtasks being used to instruct the target sub-object corresponding to the target main object to take effect in the corresponding target sub-entity, where N is equal to the number of the target sub-entities; When the execution time of the first main task reaches a preset period, the execution status of the N subtasks is counted.

4. The method according to any one of claims 1 to 3, further comprising: In response to a second configuration operation on a second batch tool of the management page of the target entity, determining an identifier of an object to be modified and attribute information to be modified, the attribute information to be modified comprising at least one of the following information: title, price, or inventory, the object to be modified comprising a main object and / or a sub-object; On the management page of the target entity, the attribute information of the object to be modified after being modified based on the attribute information to be modified is displayed.

5. The method according to claim 4, wherein The second batch tool on the management page of the target entity includes at least one of the following controls: a sixth control for triggering configuration of the attribute information to be modified, the type of the object to be modified, and the range of the object to be modified; a seventh control for triggering downloading of a template file; and an eighth control for triggering uploading of a template file. The determining, in response to the second configuration operation on the second batch tool on the management page of the target entity, of the identifier of the object to be modified and the attribute information to be modified includes: In response to operating the sixth control, displaying a third template file; In response to operating the seventh control, downloading the third template file; In response to operating the eighth control, the fourth template file is obtained, wherein the fourth template file is a file obtained by filling in the identifier of the object to be modified and the value of the attribute information to be modified in the third template file; According to the fourth template file, the identifier of the object to be modified and the attribute information to be modified are determined.

6. The method according to claim 4 or 5, wherein: Displaying, on the management page of the target entity, the attribute information of the object to be modified after being modified based on the attribute information to be modified, includes: If the type of the object to be modified is a main object, then on the management page of the target entity, the attribute information of the main object to be modified is displayed as the attribute information modified based on the attribute information to be modified; and on the management page of a child entity belonging to the target entity, the attribute information of the child object of the main object to be modified in the child entity is displayed as the attribute information modified based on the attribute information to be modified; If the type of the object to be modified is a sub-object, and the attribute information to be modified is inventory or price, then on the management page of the sub-entity belonging to the target entity, the price or inventory of the sub-object of the main object to be modified in the sub-entity is displayed as the price or inventory modified based on the attribute information to be modified.

7. The method according to any one of claims 1 to 6, further comprising: In response to a third configuration operation on a third batch tool on the management page of the target entity, displaying an export progress of the corresponding export task on a batch operation record page; In response to the export task for the object to be exported being completed, a ninth control for displaying the result download of the export task on the batch operation record page; In response to operating the ninth control, an export file corresponding to the export task is downloaded, where the export file includes a value of a preset export field of each object to be exported.

8. The method according to claim 7, wherein: The third batch tool on the management page of the target entity includes at least one of the following controls: a tenth control for triggering selection of a primary object to be exported, an eleventh control for triggering batch export configuration, a twelfth control for triggering selection of a type of object to be exported, and a thirteenth control for triggering export, and the third configuration operation includes operating the tenth control to select the primary object to be exported, operating the eleventh control, operating the twelfth control to select the type of object to be exported, and operating the thirteenth control to trigger the export task.

9. The method according to any one of claims 1 to 8, wherein: The management page of the target entity also includes a batch operation record tool, and the batch operation record page corresponding to the batch operation record tool includes at least one of the following contents: batch operation personnel, details of the batch operation, the number of main objects involved in the batch operation, or the number of sub-objects involved in the batch operation.

10. The method according to any one of claims 1 to 9, wherein: The management page of the target entity also includes at least one of the following tools: a batch listing tool, a batch delisting tool, or a batch deletion tool.

11. A batch processing device comprising: a first determining unit configured to, in response to a first configuration operation on a first batch tool on a management page of a target entity, determine a target sub-entity and a target primary object, wherein the target sub-entity is a subordinate entity of the target entity, and the target primary object is an object in the target entity, and the first batch tool is used to batch set the primary objects in the entity to the sub-entities; The first display unit is configured to display, on the management page of each target sub-entity, a target sub-object corresponding to the target main object in the target sub-entity, wherein the target sub-object has the same attribute information as the corresponding target main object.

12. An electronic device comprising a processor and a memory, wherein: The memory is configured to store instructions or programs; The processor is configured to execute the instructions or programs in the memory, so that the electronic device performs the method according to any one of claims 1 to 10.

13. A readable medium, wherein: The readable medium stores instructions or programs, and when the instructions or programs are executed on a processor, the processor is caused to execute the method according to any one of claims 1 to 10.

Images