Batch processing method and device, electronic equipment and readable medium

Abstract

The invention discloses a batch processing method and device, electronic equipment and a readable medium, in response to a first configuration operation on a first batch tool of a management page of a target entity, a target sub-entity and a target main object are determined, the target sub-entity is a subordinate entity of the target entity, and the target main object is an object in the target entity; then, target sub-objects, corresponding to the target main objects, in the target sub-entities are displayed on the management pages of all the target sub-entities, and the attribute information of the target sub-objects is the same as that of the corresponding target main objects. Therefore, a user operates the target sub-objects corresponding to the target main object in the target sub-entities in batches by using the first batch tool once, so that the target sub-objects which belong to the target sub-entities and correspond to the target main object are displayed on the management pages of the target sub-entities; a user does not need to operate the target main object and the target sub-object one by one, and the processing efficiency of the objects in the linkage entity is improved.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular, to a batch processing method, apparatus, electronic device, and readable medium. Background Art

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

[0003] 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 objects of the headquarters of the chain entity 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 need to have their own identifiers, that is, each object in a chain entity needs to have a unique identifier. In this way, when the chain entity processes its own objects, it needs to operate on each object one by one, and the processing efficiency is relatively poor. Summary of the Invention

[0004] To solve the above technical problems, this application provides a batch processing method, apparatus, electronic device, and readable medium. By operating a batch tool on the management page of the chain entity, it is possible to batch process the sub-objects corresponding to the main object in the sub-entities under the chain entity, improving the processing efficiency of the chain entity for objects in the instant retail scenario.

[0005] To achieve the above object, the technical solutions provided by this application are as follows:

[0006] In a first aspect, this application provides a batch processing method, including:

[0007] In response to a first configuration operation on a first batch tool on the management page of a target entity, determining a target sub-entity and a target main object, where 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;

[0008] On the management page of each target sub-entity, display the target sub-objects corresponding to the target main object in the target sub-entity, where the target sub-objects have the same attribute information as the corresponding target main object.

[0009] In a possible implementation, on the first batch tool on the management page of the target entity, there are a first control for triggering the selection of the main object and a second control for triggering the selection of the sub-entity. 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;

[0010] And / or, on the first batch tool on the management page of the target entity, there are a first control for triggering the selection of the 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, where the target sub-entities are all sub-entities included in the target entity;

[0011] And / or, on the first batch tool on the management page of the target entity, there are 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, where the second template file is a file obtained by filling in the identifier of the target main object and the identifier of the target sub-entity in the first template file.

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

[0013] In response to the first configuration operation, generating a first main task for instructing the sub-object corresponding to the target main object to take effect in the target sub-entity;

[0014] The method further includes:

[0015] Based on a three-level or higher-level task model, splitting the first main task into N sub-tasks, where each sub-task in the N sub-tasks is used to instruct the target sub-object corresponding to the target main object to take effect in the corresponding target sub-entity, and N is equal to the number of target sub-entities;

[0016] When the execution time of the first main task reaches a preset period, counting the execution status of the N sub-tasks.

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

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

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

[0020] In a 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 the configuration of the information on the attribute to be modified, the type of the object to be modified, and the scope of the object to be modified, a seventh control for triggering the download of a template file, and an eighth control for triggering the upload of a template file. The determining the identifier of the object to be modified and the information on the attribute to be modified in response to the second configuration operation on the second batch tool on the management page of the target entity includes:

[0021] In response to operating the sixth control, display a third template file;

[0022] In response to operating the seventh control, download the third template file;

[0023] In response to operating the eighth control, obtain a fourth template file, where the fourth template file is a file after filling in the values of the identifier of the object to be modified and the information on the attribute to be modified in the third template file;

[0024] According to the fourth template file, determine the identifier of the object to be modified and the information on the attribute to be modified.

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

[0026] If the type of the object to be modified is a main object, then on the management page of the target entity, display the attribute information of the main object to be modified as the attribute information after being modified based on the information on the attribute to be modified, and on the management page of the sub-entity belonging to the target entity, display the attribute information of the sub-object of the main object to be modified in this sub-entity as the attribute information after being modified based on the information on the attribute to be modified;

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

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

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

[0030] In response to the completion of the export task for the object to be exported, display a ninth control for downloading the result of the export task on the batch operation record page;

[0031] In response to operating the ninth control, download the export file corresponding to the export task, where the export file includes the values of preset export fields for each object to be exported.

[0032] In a 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 the selection of the main object to be exported, an eleventh control for triggering 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. The third configuration operation includes 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.

[0033] In a possible implementation,

[0034] The management page of the target entity further 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: batch operators, 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.

[0035] In a possible implementation,

[0036] The management page of the target entity further includes at least one of the following tools: a batch shelving tool, a batch unshelving tool, or a batch deletion tool.

[0037] In a second aspect, the present application further provides a batch processing device, including:

[0038] A first determination unit, configured to determine a target sub-entity and a target main object in response to a first configuration operation on a first batch tool on the management page of the target entity. The target sub-entity is a lower-level entity of the target entity, and the target main object is an object in the target entity. The first batch tool is used to batch-set the main objects in the entity into the sub-entity;

[0039] The first display unit is configured to display, on the management page of each of the target sub-entities, the target sub-objects corresponding to the target main object in the target sub-entity, where the attribute information of the target sub-objects is the same as that of the corresponding target main object.

[0040] In a possible implementation, on the first batch tool on the management page of the target entity, there is a first control for triggering the selection of the main object and a second control for triggering the selection of the sub-entity. 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.

[0041] And / or, on the first batch tool on the management page of the target entity, there is a first control for triggering the selection of the main object and a third control for triggering the 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, where the target sub-entities are all sub-entities included in the target entity.

[0042] And / or, on the first batch tool on the management page of the target entity, there is 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, where the second template file is a file obtained by filling in the identifiers of the target main object and the target sub-entity in the first template file.

[0043] In a possible implementation, the first determination unit is specifically configured to:

[0044] In response to the first configuration operation, generate a first main task, where the first main task is used to indicate that the sub-objects corresponding to the target main object take effect in the target sub-entity.

[0045] The device further includes:

[0046] A splitting unit, configured to split the first main task into N sub-tasks based on a task model of three levels or more, where each sub-task in the N sub-tasks is used to indicate that the target sub-objects corresponding to the target main object take effect in the corresponding target sub-entity, and N is equal to the number of target sub-entities.

[0047] A statistics unit, configured to, when the execution time of the first main task reaches a preset period, statistics the execution status of the N sub-tasks.

[0048] In a possible implementation, the device further includes:

[0049] A second determination unit, configured to determine an identifier of an object to be modified and information on attributes to be modified in response to a second configuration operation on a second batch tool on a management page of the target entity, where the information on attributes 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;

[0050] A second display unit, configured to display, on the management page of the target entity, information on attributes of the object to be modified after being modified based on the information on attributes to be modified.

[0051] In a 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 information on attributes to be modified, a type of object to be modified, and a scope of the object to be modified, a seventh control for triggering download of a template file, and an eighth control for triggering upload of a template file. The second determination unit is specifically configured to:

[0052] In response to operating the sixth control, display a third template file;

[0053] In response to operating the seventh control, download the third template file;

[0054] In response to operating the eighth control, obtain a fourth template file, where the fourth template file is a file after values of the identifier of the object to be modified and the information on attributes to be modified are filled in the third template file;

[0055] Determine the identifier of the object to be modified and the information on attributes to be modified according to the fourth template file.

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

[0057] If the type of the object to be modified is a main object, display, on the management page of the target entity, information on attributes of the main object to be modified as information on attributes after being modified based on the information on attributes to be modified, and display, on the management page of a sub-entity belonging to the target entity, information on attributes of a sub-object of the main object to be modified in the sub-entity as information on attributes after being modified based on the information on attributes to be modified;

[0058] If the type of the object to be modified is a sub-object and the information on attributes to be modified is inventory or price, display, on the management page of a 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 as the price or inventory after being modified based on the information on attributes to be modified.

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

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

[0061] A fourth display unit, configured to display a ninth control for downloading the 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.

[0062] A download unit, configured to download an export file corresponding to the export task in response to an operation on the ninth control, where the export file includes values of preset export fields for each object to be exported.

[0063] In a 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 main 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 the export task. The third configuration operation includes 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.

[0064] In a possible implementation,

[0065] The management page of the target entity further 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: batch operators, 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.

[0066] In a possible implementation,

[0067] The management page of the target entity further includes at least one of the following tools: a batch shelving tool, a batch unshelving tool, or a batch deletion tool.

[0068] It should be noted that for the specific implementation manner and achieved technical effects of this device, reference may be made to the relevant descriptions of the method provided in the first aspect or any implementation manner of the first aspect.

[0069] In a third aspect, the present application further provides an electronic device, where the electronic device includes: a processor and a memory;

[0070] The memory is configured to store instructions or programs;

[0071] The processor is configured 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 implementation manners of the target aspect.

[0072] In a fourth aspect, the present application further provides a readable medium, in which instructions or programs are stored. When the instructions or programs run on a processor, the processor is caused to execute the method provided by the above-mentioned target aspect or any one of the implementation manners of the target aspect.

[0073] Compared with the prior art, the embodiments of the present application have at least the following advantages:

[0074] In the technical solution provided by the present application, for a target entity belonging to a chain entity, when there is a need to batch add sub-objects corresponding to a main object to some target sub-entities in the target entity, a first batch tool is provided on the management page of the target entity. The first batch tool is used to batch set the main object in the entity to the sub-entities. The user can perform a first configuration operation on the first batch tool to quickly meet this need. Specifically, the method may include: in response to a first configuration operation on the first batch tool on the management page of the target entity, determining the target sub-entities and the target main object. The target sub-entities are the lower-level entities of the target entity, and the target main object is the object in the target entity; then, on the management pages of the respective target sub-entities, displaying the target sub-objects corresponding to the target main object in the target sub-entities, and the attribute information of the target sub-objects is the same as that of the corresponding target main object. In this way, by providing the first batch tool on the management page of the chain entity, the user can, by using the first batch tool once, based on the target sub-entities and the target main object determined by using the first batch tool this time, batch operate the target sub-objects corresponding to the target main object in the target sub-entities, so that the management pages of the respective target sub-entities display the target sub-objects belonging to the target sub-entities and corresponding to the target main object, without the user having to operate the target main object and the target sub-objects one by one based on the identifiers of different objects in the chain entity, overcoming the problem of poor processing efficiency caused by the inability to batch process the objects in the chain entity at present, improving the processing efficiency of the objects in the chain entity, and thus bringing convenience to the staff of the chain entity in the instant retail scenario. Description of the Drawings

[0075] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments recorded in the present application. For those of ordinary skill in the art, without creative efforts, other drawings can be obtained based on these drawings.

[0076] Figure 1 A flow chart of a batch processing method provided in an embodiment of the present application;

[0077] Figure 2 A schematic diagram of a batch of products provided in an embodiment of the present application;

[0078] Figure 3 A schematic diagram of another batch product provided in an embodiment of the present application;

[0079] Figure 4 A schematic diagram of another batch of products provided in an embodiment of the present application;

[0080] Figure 5 A schematic diagram of a multi-layer task model provided in an embodiment of the present application;

[0081] Figure 6 A schematic diagram of a batch modification provided in an embodiment of the present application;

[0082] Figure 7 A schematic diagram of a batch export provided in an embodiment of the present application;

[0083] Figure 8 A schematic diagram of a batch tool provided in an embodiment of the present application;

[0084] Figure 9 A schematic structural diagram of a batch processing device 900 provided in an embodiment of the present application;

[0085] Figure 10 A schematic structural diagram of an electronic device 1000 provided in an embodiment of the present application. 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 perform 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 at least include a headquarters and stores. Optionally, the chain entity may further include management unit stores for managing some of the stores. The management authority of the management unit stores is controlled by the headquarters, and the authority of the stores is jointly controlled by the headquarters and the management unit stores, with the headquarters having a higher control priority. For example, a 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. Among them, 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 embodiments of the present application, an entity may refer to the headquarters or a 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 denoted as main objects, and the objects in the sub-entity are denoted as sub-objects. A sub-object corresponds to a main object in the entity, and the attribute information of the main object and the sub-object with a corresponding relationship 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 may not have the two attributes of price and inventory. However, the sub-object needs to be displayed and sold to consumers, so in addition to including the attribute information included in the main object (such as product name, product picture, product shelf life, etc.), the sub-object also needs to include inventory and price. Suppose the attribute information of the main object 1 in entity A is attribute information 1. Then, the attribute information of the sub-object 1 corresponding to the main object 1 in a certain sub-entity a of entity A may include: attribute information 1, price = x, inventory = y.

[0089] It should be noted that the main object of the 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 objects included in the entity, or the sub-objects included in the sub-entity may partially correspond to the main objects included in the entity. For example, the headquarters of supermarket enterprise A has main product 1, main product 2, and main product 3. Supermarket enterprise A includes store 1, store 2, and store 3. The 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; the 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; the 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, the main product 1 has corresponding sub-objects in each store, the main product 2 and the main product 3 only have corresponding sub-products in some stores, and only in store 2 do the sub-objects completely correspond to the main objects of the headquarters of supermarket enterprise A, with three each, and in the other two stores, the sub-objects only partially correspond to the main objects of the headquarters of supermarket enterprise A.

[0090] In the context of instant retail, to ensure the stability and reliability of the operation 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 4 different identifiers, so that users (including consumers and the staff of entities and sub-entities) can accurately and uniquely determine the specific object based on the identifier of the object. For chain enterprises, when dealing with a main object (such as a new main object of the store goods), it is usually necessary to perform adaptive processing on the sub-objects corresponding to the main object in some or all stores. However, due to the characteristic that each object has a unique identifier, the current processing of objects within the chain entity needs to be carried out one by one, and the processing speed is very slow. Especially with more and more chain enterprises entering the online consumption platform and the continuous increase in the number of stores of chain enterprises, the staff of chain enterprises need to perform a large number of repetitive tasks on the online consumption platform, with a large workload and low work efficiency. Therefore, it has become particularly urgent to develop a batch processing tool to handle the objects within the chain entity.

[0091] Based on this, an embodiment of the present application 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 a target sub-entity and a target main object, where 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 pages of the respective target sub-entities, display the target sub-objects corresponding to the target main object in the target sub-entity, and the attribute information of the target sub-objects 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 some target sub-entities in the target entity, a first batch tool is provided on the management page of the target entity. The user only needs to perform a first configuration operation on the first batch tool to quickly achieve this need, that is, the user, by using the first batch tool once, based on the target sub-entity and the target main object determined by this use of the first batch tool, batch operates on the target sub-objects corresponding to the target main object in the target sub-entities, so that the management pages of the respective target sub-entities display the target sub-objects belonging to the target sub-entity and corresponding to the target main object, without the user having to operate on the target main object and the target sub-objects one by one based on the identifiers of different objects within the chain entity, overcoming the problem of poor processing efficiency caused by the inability to batch process objects in the current chain entity, improving the processing efficiency of objects in the chain entity, and thus bringing convenience to the staff of the chain entity in the instant retail scenario.

[0093] In addition, in the embodiments of the present application, batch tools with other functions are also provided, and these batch tools can all achieve batch processing of corresponding functions for objects in chain entities. The above-mentioned first batch tool can be understood as a tool for realizing batch product placement, and other batch tools may also include, but are not limited to: batch modification tools, batch export tools, batch operation record tools, batch listing tools, batch delisting tools, or batch deletion tools.

[0094] It should be noted that the main body implementing this batch processing method can be the batch processing device provided in the embodiments of the present application. This batch processing device can be carried on an electronic device or a functional module of an electronic device. For example, this batch processing device can be a work website provided by an online consumption platform for the staff of a chain entity to use, or a functional module on the server corresponding to this website, realizing the batch processing function provided in the embodiments of the present application.

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

[0096] Figure 1 It is a schematic flowchart of a batch processing method provided in the embodiments of the present application. This method can be applied to a batch processing device, and this batch processing device can be, for example, Figure 9 the batch processing device 900 shown below.

[0097] As Figure 1 shown, this method can, for example, include the following S101 to S102:

[0098] S101, in response to a first configuration operation on a first batch tool on the management page of a target entity, determine a target sub-entity and a target main object. The target sub-entity is a lower-level entity of the target entity, and the target main object is an object in the target entity. This first batch tool is used for batch setting of the main object in the entity into the sub-entity.

[0099] The target entity can refer to the headquarters or any level of management unit store of any entity with batch processing requirements among the chain enterprises settled in the online consumption platform in the instant retail scenario. The staff of the target entity can log in to the work website provided by the consumption platform for the staff of this target entity through methods such as account-password or account-verification code, and realize the management of the target entity through operations on the management page of this work platform.

[0100] In the embodiments of the present application, a management page of a target entity may include a plurality of tools for batch processing, and at least the first batch tool may be included in the plurality of tools. According to its function, the first batch tool may also be referred to as a batch product placement tool, that is, the target main objects determined to be placed into the sub-entities in the target entity are placed into the determined target sub-entities, so that the target sub-entities include target sub-objects corresponding to the target main objects.

[0101] Among them, the target sub-entities may refer to several lower-level entities of the target entity. For example, if the target entity is the headquarters of Chain Enterprise A, the target sub-entities are any one of the stores belonging to Chain Enterprise A; or, if the target entity is any one of the management unit stores a of Chain Enterprise A, the target sub-entities are several stores belonging to the management unit store a of Chain Enterprise A.

[0102] The target main objects are several objects in the target entity, and the target sub-objects are several objects in the target sub-entities. The "main" and "sub" before the objects are names defined to distinguish the two. The main objects only exist in the entity, and the sub-objects only exist in the sub-entity. The main objects cannot be displayed and sold to consumers, while the sub-objects can be displayed and sold to consumers. For example, taking Chain Enterprise A as the target entity, its headquarters includes ten different types of milk: Milk 1 to Milk 10, and Milk 1 to Milk 10 can be understood as 10 main objects of the target entity; if Milk 1 to Milk 8 are placed in Store 1 of Chain Enterprise A, and Store 1 is used as the target sub-entity, then Milk 1 to Milk 8 can be understood as 8 sub-objects of the target sub-entity.

[0103] For batch product placement of the target entity using the first batch tool, the existing scenarios may include but are not limited to: Scenario 1, select multiple target main objects and configure them with one key to all target sub-entities of the target entity; Scenario 2, select multiple target main objects and configure them with one key to at least one target sub-entity of the target entity; Scenario 3, select one target main object and configure it to multiple target sub-entities of the target entity. It should be noted that for chain enterprises, usually all main objects are placed in all target sub-entities, and by preventing the sub-objects in the target sub-entities from switching to the "on-shelf" state, or setting the inventory of the sub-objects in the target sub-entities to 0, etc., the sale of the sub-objects by the target sub-entities is restricted. Therefore, the application scenario of Scenario 3 is less.

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

[0105] In some possible implementations, the first batch tool can provide multiple ways to implement batch product placement for users to select and use. That is, different ways of batch product placement correspond to different first configuration operations on the first batch tool. Three possible ways of batch product placement are introduced below.

[0106] As an example, on the first batch tool of the management page of the target entity, it can at least include: a first control for triggering the selection of the main object and a second control for triggering the selection of the sub-entity. Then, the first configuration operation can include: 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.

[0107] Optionally, in this example, the first batch tool may also include, for example, 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 list the target sub-object with the price and inventory configured.

[0108] For example, see Figure 2 As shown, taking the first batch tool as the tool corresponding to batch product placement, the object is a commodity, the main object is the main commodity, and the sub-entity is a store as an example. 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 as Figure 2 shown in the upper left corner. Under commodity management, it can include batch product placement, batch export, batch modification and other batch tools. When the user clicks the "Batch Product Placement" button, the management page is as Figure 2 shown in the upper right corner. The user can first select the main commodity to be placed, and then select the store to which the product is to be placed, and then submit the current batch product placement process; when the user is in Figure 2 the page shown in the upper right corner and selects the main commodity, clicks "Next", the management page is as Figure 2 shown in the lower right corner. When the user is in Figure 2 the page shown in the lower right corner and selects the store, clicks "Submit", the management page is as Figure 2 shown in the lower left corner. Among them, the operation of the user selecting the main commodity in Figure 2 the page shown in the upper right corner corresponds to the part of operating the first control in the first configuration operation, and the operation of the user selecting the store in Figure 2 the page shown in the lower right corner corresponds to the part of operating the second control in the first configuration operation.

[0109] For the way of selecting the main commodity that needs to be placed, such as Figure 2As shown in the upper right corner, it may include: Method 1, select all main products; Method 2, select main products by category; Method 3, select main products by product identifier (ID).

[0110] For Method 1, the scope of all main products is related to the permissions of the department to which the logged-in user of the current working website belongs. If the currently logged-in User A belongs to the headquarters, all main products are all the main products released by the headquarters and stocked; if the currently logged-in User A belongs to a certain management unit store, all main products are all the main products of the stocked products of that management unit store.

[0111] For Method 2, you can first select a category template and then select the specific categories under the selected category template. The logic for the default selection of the category template can be single selection, that is, when there is 1 effective category template, then the category template is default selected; when there are multiple effective category templates at the same time, then you can select the category template that was last modified among the effective category templates. After selecting the category template, the process of selecting specific categories may include: First, click "Add products under category", then the categories in the selected category template will be cascaded and displayed on the page in the form of a drawer, etc.; Next, select the specific categories in the category template, where multiple selections are allowed, and "All categories" is also supported. If "All categories" is selected, then all categories under the category template will be selected. If no category is selected, the "OK" button on the page for selecting specific categories cannot be operated; Then, click the "OK" button on the page for selecting specific categories, return to the page for batch stocking products, and display the selected specific categories. When displaying the categories, at least one of the following information can be displayed: category information (the finest level of the category) and the number of main products included in the category. It should be noted that when the selected category contains Mendeleev categories and directly mounts products, the number of main products included in the category includes the sum of the number of products under the Mendeleev categories and the number of directly mounted products. For example, if the selected category (such as "Essentials for Hot Pot") contains 3 Mendeleev categories (a total of 300 products) and directly mounts 30 products at the same time, then 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 will be cleared, and specific categories need to be re-selected under the new category template. It should be noted that when "Select by category" is selected, it can be prompted in the form of a pop-up window or a prompt message that categories cannot be modified. For example, display the prompt text "When selecting to add products by category, do not modify the categories, as it may affect the selection of the number of products."

[0112] For Method 3, it applies to the case of known product IDs. During the process of inputting the main product ID, when the "Add Product ID" button is clicked, an ID input pop-up window will appear. This pop-up window is used to prompt the user about the rules for inputting product IDs. For example, the copywriting of this pop-up window can be "Please input product IDs, which can be on separate lines or separated by commas. At most x products can be selected at a time", where x is the preset upper limit for the number of products input at one time. Multiple clicks on the "Add Product ID" button are supported. For example, when the "Add Product ID" button is clicked for the first time and 100 product IDs are input, then click "OK"; then click the "Add Product ID" button again, input another 100 product IDs, and click "Confirm", then a total of 200 products are added in two times. The input box can display the number of products already added this time and the remaining number of products that can be added. The format can be, for example: Number of products already added this time / Remaining number of products that can be added. When the limit for the maximum number of main products selected in one batch of product placement is 500, if the number in the first add pop-up window is: xx / 500 and 150 products are added; the number in the second add pop-up window can be zz / 350, where xx is the number of products already added at the moment of the first display, and zz is the number of products already added at the moment of the second display. 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), clicking "OK" is prohibited, and the maximum quantity limit is highlighted or a pop-up window is used to prompt to delete some product IDs; if the added product IDs are not in the normal selling status, the product IDs are marked in red to avoid the failure of product placement display after all submissions. When there are verification errors, it can be prompted that "Some product IDs cannot be recognized or the product IDs are incorrect. Please modify and continue to add. You can also click [One-Click Clear] to remove the unrecognized product IDs". If the user clicks [One-Click Clear], only the correctly recognized and existing product IDs will be retained. After the step of inputting product IDs is completed, the selected products are displayed in a drawer or other way on the page. The displayed product information can 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 can also include the number of selected products (such as "x products selected"). On this display page, the user can click the "Delete" button for a single product to delete it. On this display page, the user can click "Clear Selected" to clear all selected products.

[0113] For all selected main products, the prices and stocks of sub-products can also be set in batches. For price setting, "Keep the same as the main product" is selected by default. "Custom input" can also be selected, and the custom price can be entered in the displayed input box. For stock setting, the default stock is 0. "Keep the same as the main product" can be selected, and "Custom input" can also be selected, and the custom stock can be entered in the displayed input box. Hint text can be displayed in the input box, such as "Please enter the stock". When the stock 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 stock quantity or price will be marked in red, or the reason for the error will be prompted through a pop-up window. Optionally, the online status of sub-products can also be selected. The options can include default online and default offline. If default online is selected, the sub-product will be default online after the sub-product is added successfully. If default offline is selected, the sub-product will be default offline after the sub-product is added successfully.

[0114] After the selection of the main product is completed in this example, when the quantity of the selected main product is 0, it is not allowed to click "Next" to continue selecting the target sub-entity. If the stock of the sub-product is configured, when the configured stock is less than 0 or not an integer, it is not allowed to click "Next" to continue selecting the target sub-entity.

[0115] Regarding the step of selecting the stores to which the products are to be distributed, it should be noted that the operation of batch distribution of products is only effective for stores that are in normal business and stores that are suspended. Batch distribution of products cannot be achieved for stores in other states. Therefore, when using this batch distribution function, a prompt such as "Only effective for stores in normal business and stores that are suspended. Please confirm the store status in advance" can be given through a pop-up window or prompt message.

[0116] Regarding the method of selecting the stores to which the products are to be distributed, as Figure 2 shown in the lower right corner, it can include: Method 1, select all stores; Method 2, select stores by management unit store; Method 3, select stores by store ID.

[0117] For Method 1, the scope of all stores is related to the permissions of the department to which the logged-in user of the current work website belongs. If the currently logged-in user A belongs to the headquarters, all stores are all the stores under the headquarters. If the currently logged-in user A belongs to a certain management unit store, all stores are all the stores controlled by the management unit store. Optionally, the user can be prompted with "Only addable to the stores to which this account has permissions, a total of xx stores", where the number of stores is the stores that are currently in business and suspended under the current account.

[0118] For Method 2, you can first click "Add Store for Merchandise Placement", and then the organizational hierarchy will be cascaded and displayed in the form of a drawer or other means on the page for the user to select stores. Only the stores that the currently logged-in and successful account has permission to control will be displayed on this drawer page. Multiple stores can be selected, or "All Stores" can be selected. If "All Stores" is selected, all stores under this management unit store will be selected. If no store is selected, the "OK" button on the page for selecting specific stores cannot be operated. Then, click the "OK" button on the page for selecting specific stores to return to the page for batch merchandise placement, and the selected specific stores will be displayed. When displaying the stores, at least one of the following information can be shown: store information (such as store name, store ID, etc.), information of the management unit store to which it belongs (displaying multi-level classification, separated by " / ", such as "A Supermarket / B Region"), store address, and operations (such as deletion). The displayed content can also include the number of selected stores (such as "x stores selected"). On this display page, the user can click the "Delete" button to delete a single store. On this display page, the user can click "Clear Selected" to clear all selected stores.

[0119] For Method 3, it applies to the case of known store IDs. During the process of inputting store IDs, when the "Add Store ID" button is clicked, an ID input pop-up window will appear. This pop-up window is used to prompt the user about the rules for inputting store IDs. For example, the copywriting in this pop-up window can be "Please input store IDs, which can be entered on separate lines or separated by commas. At most x stores can be selected at one time", where x is the preset upper limit for the number of stores input at one time. Multiple clicks on the "Add Store ID" button are supported. For example, when the "Add Store ID" button is clicked for the first time and 100 store IDs are input, then click "OK"; when the "Add Store ID" button is clicked again and another 100 store IDs are input, then click "Confirm", so a total of 200 stores are added in two times. The input box can display the number of stores already added this time and the remaining number of stores that can be added. The format can be, for example: the number of stores already added this time / the remaining number of stores that can be added. When the limit for the maximum number of stores selected in a single batch of product placement is 500, if the number in the first add pop-up window is: xx / 500 and 150 stores are added; the number in the second add pop-up window can be zz / 350, where xx is the number of stores already added at the moment of the first display, and zz is the number of stores already added at the moment of the second display. For the reliability of this method, quantity verification and status verification will be carried out. That is, when the number of selected stores exceeds the maximum quantity limit (such as 500), the "OK" button is prohibited from being clicked, and the maximum quantity limit is highlighted or a pop-up window is used to prompt to delete some store IDs; if the added store IDs do not belong to normal operation or are suspended, the store IDs will be marked in red to avoid the failure of displaying the products after all are submitted. When there are verification errors, it can be prompted that "Some store IDs cannot be recognized or the store IDs are incorrect. Please modify and continue to add. You can also click [Clear All] to remove the unrecognized store IDs". If the user clicks [Clear All], only the correctly recognized and existing store IDs will be retained. After the step of inputting store IDs is completed, the selected stores will be displayed on the page in the form of a drawer or the like, showing at least one of the following information: store information (such as store name, store ID, etc.), information of the management unit store to which it belongs (displaying multi-level classification, separated by " / ", such as "A Supermarket / B Region"), store address, and operations (such as deletion). The displayed content can also include the number of selected stores (such as "x stores have been selected"). On this display page, the user can click the "Delete" button for a single store to delete it. On this display page, the user can click "Clear Selected", and then all the selected stores will be cleared.

[0120] After the selection of stores is completed in this example, when the number of selected stores is 0, the "Submit" button is not allowed to be clicked.

[0121] After the selection of stores is completed, when the "Submit" button is clicked, a pop-up window can be displayed. The pop-up window can be, for example, as Figure 2As shown in the lower left corner, 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, it takes a certain amount of execution time. Closing this page will not abort 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 will jump to the display page corresponding to the batch operation result. If the user clicks "Continue Product Placement", it will return to the first step of the page corresponding to batch product placement. For example Figure 2 The initial state of batch product placement as shown in the upper right corner.

[0122] As another example, on the first batch tool of the management page of the target entity, it can at least include: a first control for triggering the selection of the main object and a third control for triggering the application to all child entities. Then, the first configuration operation can include: 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 child entities of the target entity. In this example, the target child entities are all child entities included in the target entity.

[0123] For example, see Figure 3 As shown, taking the first batch tool as the tool corresponding to batch product placement, the object is a product, the main object is the main product, and the child entity is a store. After 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 as Figure 3 As shown in the upper left corner, under product management, it can include batch product placement, batch export, batch modification and other batch tools. When the user clicks the button "Batch Product Placement", the management page is as Figure 3 As shown in the upper right corner, all main products that can be placed are displayed. The user can first select at least one main product to be placed, and then click "Place to All Stores" to complete the current batch product placement process. The management page is as Figure 3 The page shown in the lower right corner. A prompt "Confirm to place goods to all stores?" is given through a pop-up window or other means. The body text of this pop-up window can be "After the store configuration is successful, the product will be submitted for review and automatically put on the shelf for sale. This operation only places goods for the stores with permissions under the account, and the stores that have been configured will not be placed again". This pop-up window has two operations: "Confirm" and "Cancel"; if the user clicks the "Confirm" button, the management page is as Figure 3The page shown in the lower left corner displays "Operation Result" through a pop-up window or other means. The body text of the pop-up window can be "The store merchandise placement is in progress and will take 3 to 5 minutes to take effect. You can view the merchandise placement result in [Batch Operation Record]. Please wait patiently." The pop-up window has two operations: "View Batch Operation Record" and "Close". When the user clicks "View Batch Operation Record", it will jump to the page corresponding to the batch operation record to view the merchandise placement result. When the user clicks "Close", it will return to the first step of the page corresponding to the batch merchandise placement. For example Figure 3 The initial state of the batch merchandise placement shown in the upper right corner.

[0124] Among them, when the user is in Figure 3 the operation of selecting the main product on the page shown in the upper right corner corresponds to a part of the first operation control in the first configuration operation. When the user is in Figure 3 the operation of clicking "Place Merchandise to All Stores" on the page shown in the upper right corner corresponds to a part of the third operation control in the first configuration operation.

[0125] Such as Figure 3 As shown in the upper right corner, the page corresponding to the batch merchandise placement displays a list of main products that can be selected. The page also includes a general "Place Merchandise to All Stores" button. Each main product corresponds to a selection box. Optionally, the operation corresponding to each main product can also include an option of "Place Merchandise to All Stores". In this way, when the user wants to place the merchandise of a certain main product to all stores, in one case, the user can check the selection box corresponding to the main product and then click the general "Place Merchandise to All Stores" button to complete the operation of placing the merchandise of the main product to all stores. In another case, the user can also check the selection box corresponding to the main product and then click the "Place Merchandise to All Stores" button in the operation option corresponding to the main product to complete the operation of placing the merchandise of the main product to all stores. When the user wants to place the merchandise of multiple main products to all stores, the user can check the selection boxes corresponding to the multiple main products and then click the general "Place Merchandise to All Stores" button to complete the operation of placing the merchandise of the multiple main products to all stores.

[0126] In this example, it supports batch adding of main products with certain common features filtered out to all stores. When no main product is checked, the "Place Merchandise to All Stores" cannot be clicked. Only after at least one main product is checked can the "Place Merchandise to All Stores" be clicked.

[0127] It should be noted that for batch product placement, when the selected main product has been placed in some stores, no repeated product placement will be carried out, nor will the prices and inventories of the placed sub-products be modified according to the set prices and inventories. For example, if the main product A has placed the sub-product a in store 1, the price of this sub-product is 15 yuan and the inventory is 20. If "main product A" is selected at this time and "Place products to all stores" is clicked, and the prices of all stores are set to 18 yuan and the inventory is 999, then after the operation of this batch product placement is completed, the price of the sub-product a in store 1 is still 15 yuan and the inventory is still 20. The operation of this batch product placement only affects the prices and inventories of the sub-products placed for the first time.

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

[0129] It should be noted that when an error occurs, the embodiment of the present application also includes a "Download Results" button. When the user clicks this button, a table including information such as the error location and error reason can be downloaded for the user to analyze the error and maintain the tool.

[0130] If the batch product placement is successful, the store can receive a message indicating successful product placement and conduct an inventory count and verification. If the batch product placement fails, a table including the reasons for failure can be downloaded. The reasons for failure include factors in two dimensions: the main product and the store. For example, an abnormal store status is one of the reasons for the failure of batch product placement; after the batch product placement fails, the batch product placement can be carried out again.

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

[0132] In the current two - layer task model, a main task is serially split into multiple subtasks, and each subtask is used to perform corresponding business operations. Taking the main task of distributing the main product a to stores 1, 2, and 3 as an example, the main task can first be split into subtask 1 (i.e., distributing the main product a to store 1), then subtask 2 (i.e., distributing the main product a to store 2), and then subtask 3 (i.e., distributing the main product a to store 3). Finally, subtask 1, subtask 2, and subtask 3 perform specific distribution actions, so that stores 1, 2, and 3 respectively have sub - products a1, a2, and a3 corresponding to the main product a. It can be seen that the most influential factor in the time consumption of this main task is the splitting of the main task. In this two - level task model, the main task is serially split into multiple subtasks. The more subtasks need to be split, the longer the time consumption, resulting in a relatively long overall time consumption of the main task. Based on this, in order to improve the processing efficiency of the main task, the embodiments of this application propose a strategy for executing the main task based on a three - layer or more task model. It should be noted that regardless of the number of layers of the task model, the actual business operations are performed by the leaf nodes of the last layer.

[0133] Taking a four - layer task model as an example, the process of splitting the first main task can include: First, aggregate the main products of the first main task to obtain second - layer subtasks; then, process the second - layer subtasks according to the main products and stores to obtain third - layer subtasks; then, for the third - layer subtasks, obtain fourth - layer subtasks according to the sub - products to be distributed at the right time. Among them, the fourth - layer tasks are used to perform corresponding business operations. Whether it is the main product or the store, since they are decoupled, the task splitting of each layer can be executed in parallel, which can effectively improve the efficiency of splitting the main task, thereby improving the efficiency of executing the main task.

[0134] Taking Figure 5 as an example, main task 1 can first be split into subtasks 11 - 15 according to the aggregation result of the main products; subtasks 11 - 14 are split according to the main product + store, and respectively obtain {subtasks 211 and 212}, subtask 221, subtask 231, and {subtasks 241 and 242}; subtasks 211, 212, 221, and 231 are split according to the sub - products, and respectively obtain subtasks 341, 342, 343, and 344. Among them, the subtasks responsible for performing business operations can include: subtask 15, subtasks 241, 242, 341, 342, 343, and 344. Compared with the two - layer task model, the time consumption of executing the main task is significantly reduced, and moreover, 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 currently, transactions are immediately initiated to update the status of the upper-level task (i.e., the main task) (the completion status of the subtasks can be understood by counting). In some cases, a large number of subtasks will update the status of the same main task within a short period of time. Since only one transaction can actually update the status of the main task at the same time and other transactions have to wait, it will cause problems such as excessive write hot rows and database connection counts. Based on this, in the embodiments of the present application, in order to improve the above problems when updating the status of the main task, an implementation method of the main task periodically sweeping back is proposed to update the status of the main task, that is, the main task periodically checks and records the situation of the subtasks completed during this period (such as the number of successfully executed subtasks, the number of failed subtasks, etc.), without each subtask updating the status of the main task one by one.

[0136] Corresponding to Figure 1 For the method shown, after generating a first main task in response to the first configuration operation, the method may further include: based on a task model of three levels or more, splitting the first main task into N subtasks, where each subtask in the N subtasks is used to indicate that a target sub-object corresponding to the target main object takes effect in a 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 each time, counting the execution situation of the N subtasks to update the status of the first main task.

[0137] It can be seen that through S101, determining the target main object to be covered and the target sub-entities to which the covering is to be performed provides data support for batch covering.

[0138] S102, on the management page of each target sub-entity, display the target sub-objects corresponding to the target main object in the target sub-entity, and the attribute information of the target sub-objects is the same as that of the corresponding target main object.

[0139] In the embodiments of the present application, based on the first configuration operation, the target main object and the target sub-entities can be determined. Then, the first batch tool can cover the target sub-objects corresponding to the target main object in each target sub-entity to the corresponding target sub-entities. In this way, on the management pages of the target sub-entities to which the covering is to be performed, the user can see the target sub-objects to be covered. In this way, there is no need for the user to manually perform covering one by one, which greatly improves the efficiency of covering.

[0140] In some possible implementations, if the first batch tool does not provide the function of setting the price and inventory of sub-objects, 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 the batch products to be listed in this embodiment of the present application, a second batch tool for batch modification is also provided. Specifically, the method may further include: S103, in response to a 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 information of the attribute to be modified; S104, on the management page of the target entity, displaying the attribute information of the object to be modified after being modified based on the information of the attribute to be modified. Among them, the information of the attribute 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, on the second batch tool on the management page of the target entity, there may be at least one of the following controls: a sixth control for triggering the configuration of the information of the attribute to be modified, the type of the object 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 a third template file; in response to operating the seventh control, downloading the third template file; in response to operating the eighth control, obtaining a fourth template file, where the fourth template file is a file after filling in the values of the identifier of the object to be modified and the information of the attribute to be modified in the third template file; then, based on the fourth template file, determining the identifier of the object to be modified and the information of the attribute to be modified.

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

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

[0144] For the tool 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 template; 2. Fill in content; 3. Upload file; 4. Submit modification".

[0145] Among them, when downloading the modification template, first, the optional items of the attribute information to be modified can include: price, title, and inventory, and only one optional item can be selected; the optional items of the object type to be modified can include: main commodity and sub-commodity, and only one optional item can be selected. Moreover, since the title information of the main and sub-commodities cannot be differentiated, when the main commodity modifies the title information, the sub-commodities will be modified simultaneously. Therefore, when the content to be modified is selected as "title", the selection of the commodity type can be hidden, and a prompt copy can be added: "Only the title of the main commodity can be modified. After the title of the main commodity is modified, the sub-commodities associated with the main commodity will be modified simultaneously". There are three ways to configure the scope of the object to be modified. For details, see the above S101 regarding Figure 2The example shown is a description of three ways to select the main object. 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, for example Figure 6 The initial state of the batch edit is shown in the upper right corner.

[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". If the product has multiple specifications, fill in "all / all" if all specifications need to be modified. 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 only exists when the modification content is "price". , required, the unit can be yuan, and it can be accurate to 0.01 at most. If it is not filled in, it will not be modified, the processing will fail and an error will be reported. If the store has no sub-products, it will be skipped and not processed; e) Inventory, this column is only available when the modification content is "Inventory", required, the value is an integer greater than or equal to 1, and the upper limit can be 999999. If it is not filled in, it will not be modified, the processing will fail and an error will be reported. If the store has no sub-products, it will be skipped and not processed; f) Title, this column is only available when the modification content is "Title", required, if it is not filled in, it will not be modified, 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", there is no this column, 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 supported upload file formats may include excel files. The template header verification can be understood as: based on the selected modified attribute information and the 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 Modifications" at the bottom. After clicking "Submit Batch Modifications", you can refer to Figure 6As shown in the lower left corner, prompt "Upload Result" through pop-up windows or other means. The copywriting of the pop-up window can be "The batch modification submission is successful. Due to the large amount of data, it takes a certain execution time. Closing this page will not abort the batch modification operation. You can view the operation result 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", it will jump to the page corresponding to [Batch Operation Record]. If you click "Close", it will return to the first step of the page corresponding to batch modification. For example Figure 6 The initial state of batch modification shown in the upper right corner.

[0149] When the modification object type is sub-product, the processing for export failure can include: the import limit can be set to 50,000. For the exceeded part, no processing will be done and the export failure will be directly confirmed. The error message can be: Exceeded the upper limit of the number of stores set at one time. Please upload again. In order for users to directly modify and import after exporting the failure record, the reason for failure needs to be pointed out in the error message so that users can modify according to the reason for failure. In the file imported by the merchant, add a failure record table. After downloading, this table will be selected by default. In the embodiments of the present application, the failure records can be generated by type.

[0150] When the object type to be modified is the main product, if the modified attribute information is the title, the modification of the main product will be default synchronized to the sub-products, so the modification result of only the main product can be shown in the result. If the modified attribute information is the price, both the modification error of the main product and the modification error of the sub-products are output; flatten all modification contents (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 stores; for the field description of the result download, 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 show the reason for failure). If the modified attribute information is the inventory, both the modification error of the main product and the modification error of the sub-products are output; flatten all modification contents (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 stores; for the field description of the result download, 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 show the reason for failure).

[0151] After executing S101~S104, the target sub-entity can perform operations such as putting on the shelf, taking off the shelf, and deleting on its own target sub-object.

[0152] In some possible implementations, chain enterprises are concerned that some stores may modify the product attribute information of the sub-products they sell. Therefore, there is a need to batch export the product attribute information of the sub-products corresponding to the main products they are interested in at some stores, in order to verify the product attribute information (especially price and inventory). Therefore, the batch tool provided in the embodiments of the present application may further include a corresponding batch export tool (i.e., the third batch tool). Specifically, the embodiments of the present application may further include: First, in response to a 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; Next, in response to the completion of the export task for the object to be exported, a ninth control for triggering the download of the result of the export task is displayed on the batch operation record page; Then, in response to operating the ninth control, the export file corresponding to the export task is downloaded, and the export file includes the values of the preset export fields for each object to be exported. In this way, through the batch export tool, it is convenient for users to quickly obtain the product attribute information corresponding to at least one main product in multiple stores they are concerned about. It should be noted that the corresponding batch export tool can be used by the headquarters, management unit stores, or stores with permissions.

[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 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 batch export tool 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, see Figure 7As shown, in the tool for batch export, multiple selected main products can be displayed by filtering at least one condition among the commodity selling price range, commodity type, or commodity sales volume. Each main product corresponds to a checkbox and can be selected as the target for batch export. The drop-down menu of "Batch Operations for Sub-products" can also include the option of "Export Sub-products"; each main product's operation item can also separately correspond to an option of "Export All Sub-products"; users can batch export the sub-products corresponding to the selected main products by clicking on the above options of "Export Sub-products" or "Export All Sub-products". After clicking on the option of "Export Sub-products" or "Export All Sub-products", a page corresponding to the batch export of products can be displayed in a drawer or other way. On this page, the product type to be exported and the report fields to be displayed can be selected. Among them, the product type to be exported includes two radio buttons: "Export Only Main Products" and "Export Main Products and All Sub-store Sub-products under This Product". It should be noted that the upper limit of the main products selected for a single batch export can be set, such as 10. Then, at the top of the page corresponding to the batch export of products, a prompt can be displayed, and the text can be "To ensure that the export result can be opened and used normally, the batch export sub-product function supports selecting up to 10 main products at most", and the proportion of the currently selected main products can be displayed on the far right of this prompt, such as 1 / 10. The font or background color of this prompt can be used to distinguish whether the selected main products exceed the preset upper limit. For example, if not exceeded, the font is green, and if exceeded, the font is red.

[0156] For batch export, the attribute information of the exported sub-products can be preset according to requirements. For example, the attribute information of the exported sub-products can 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 item number. It can also include: store ID, main product ID, or main product status. It should be noted that the main product information needs to be exported simultaneously, and the main product and sub-product types should be marked. If the store ID corresponding to the main product can be filled with "none"; the export quantity does not exceed 200,000. If it exceeds 200,000, the export will fail, and a prompt will be given: "The number of sub-products exceeds 200,000, and export is not supported. Please contact the customer service for handling"; if some fields in the sub-product information are empty, it does not affect the entire export task; there is no need to distinguish the main and sub-products into different tables, and they can be exported in the same table.

[0157] For the export operation entry, the operation items for each main product include the option of "export all sub-products". After clicking, a confirmation pop-up window will appear. After clicking "OK" in the confirmation pop-up window, the generation of the export task will be triggered. If the option of "export the main product and all sub-products of this store under this product" is selected, then the main product and all sub-products will be exported; if the export product type is switched to "export only the main product", then only the information of the main product will be exported. The report fields need to list all the exported fields. Optionally, the number of the current exported main products can also be prompted at the bottom.

[0158] After the export task is triggered, it can be prompted that "the export has started. Please go to the batch operation record page to view the export result later". If the export quantity exceeds the set upper limit, a failure prompt can be added to the corresponding row of the export task of this batch export on the corresponding page of the batch operation record to prompt the user. For example, for the export task with a batch export exceeding 200,000, it is set as a failed task. The failure reason can be "partially failed, exceeding the upper limit of 200,000", the failure prompt can be "exceeded the limit", and the prompt text can be "the quantity of exported products has exceeded the upper limit of 200,000, and the exceeded part has failed to be exported. Please check and export separately". For the export tasks of batch export, on the corresponding page of the batch operation record, a record function corresponding to "export all sub-product tasks" is added. The operation status can include: in progress (the text can be "in progress"), task completed (the text can be "completed"), and task failed (the text can be "processing failed"); if the operation is successful, a function to download the export result is added, and the file of the batch export can be directly downloaded. If the operation fails, it can be retried to re-export the sub-products, but the corresponding newly generated export task will be retried. It should be noted that if there is an ongoing export task, a new export task cannot be initiated, and a prompt will be given that "there is already an ongoing export task. Please retry after it ends. Whether to end the ongoing export task can be viewed on the corresponding page of the batch operation record". For the convenience of users to view, a new export record can also be added to the "historical report" of the export record. If the export is successful, "download" can be directly clicked, and if it fails, "retry" can be directly clicked.

[0159] The above description can be applied to the case of selecting "export all sub-products" for a single main product. For the case of selecting "export sub-products" for multiple main products, when selecting the option of "export the main product and all sub-products of this store under this product", the upper limit of the number of selected main products can also be set. For example, only 10 main products can be selected for export of sub-products. If more than 10 main products are selected, the "export" button cannot be operated; for the option of "export only the main product", the number of selected main products is not restricted. The export results can all be viewed on the corresponding page of the batch operation record.

[0160] In some possible implementations, the batch tool provided in the embodiments of the present application may further include a batch operation record tool. Specifically, at least one of the following may be included on the batch operation record page corresponding to the batch operation record tool: the batch operator, the 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 record tool supports viewing each batch operation. For example, the operation status of each batch operation (such as in operation, operation successful, operation failed, etc.) can be viewed. In addition, the details of the batch operation (such as the details of successful products, the details of failed products, etc.) can also be displayed, and subsequent actions can be guided (such as guiding to display products for products successfully released, guiding to view the reason for products with failed release, guiding to modify and supplement 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 is retained.

[0162] As an example, the content recorded in the batch operation record may include: filtering options, operation columns, and a batch operation list.

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

[0164] In the operation column, "Details of Batch Operations" can be added to record all possible information for subsequent statistics, analysis, verification, etc. of each batch operation for users. For different types of batch operations, the specific content included in the details of batch operations is introduced. For batch creation, the details of batch operations can specifically record: a) The operation type, which can be batch creation; b) The operation time, which can be accurate to the second, such as "2023-11-12 22:59:33"; c) The operator; d) Uploaded attachments, which can record the names of the uploaded attachments, and downloading the uploaded attachments is not supported. For batch product placement (including the function of one-key configuring a single main product to all stores, the function of adding new stores, and the batch product placement function), the details of batch operations can specifically record: a) The operation type, which can be batch product placement; b) The operation time; c) The operator; d) The selected products, which can display a list of products (such as product name, product ID, price, release date, etc.); e) The selected stores, which can display a list of stores (such as store name, store ID, etc.); f) Price and inventory, which can record the options during the batch operation. If "Keep the same as the main product" is selected, then "Keep the same as the main product" is displayed. If "Custom input" is selected, then the custom input value is displayed. For batch listing, the details of batch operations can specifically record: a) The operation type, which can be batch listing; b) The operation time, which can be accurate to the second, such as "2023-11-12 22:59:33"; c) The operator; d) The operation scope, which can be displayed according to the selection during the batch operation. If "List the main product and sub-products simultaneously" is selected, then "List the main product and sub-products simultaneously" is displayed. If "List only the main product" is selected, then "List only the main product" is displayed; e) The 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 batch operations can specifically record: a) The operation type, which can be batch delisting; b) The operation time, which can be accurate to the second, such as "2023-11-12 22:59:33"; c) The operator; d) The 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 batch operations can specifically record: a) The operation type, which can be batch deletion; b) The operation time, which can be accurate to the second, such as "2023-11-12 22:59:33"; c) The operator; d) The 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 batch operations can specifically record: a) The operation type, which can be batch modification; b) The operation time, which can be accurate to the second, such as "2023-11-12 22:59:33"; c) The operator; d) Uploaded attachments, which can record the names of the uploaded attachments, and downloading the uploaded attachments is not supported.For batch export, the details of the batch operation can be specifically recorded as follows: a) The operation type, which can be batch export or data export; b) The operation time, which can be accurate to the second, such as "2023-11-12 22:59:33"; c) The operator; d) The export scope, which can be displayed according to the selection during batch export. If "only export main products" is selected, then "only export main products" will be displayed; if "export main products and all sub-products of the store under this product" is selected, then "export main products and all sub-products of the store 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-products may include: a) Total, used to record the number of sub-products to be delisted this time; b) Success, used to record the number of successfully delisted sub-products; c) Draft box, since there is no process of putting items into the draft box for batch delisting, it can be shown as "-"; d) Failure, used to record the number of sub-products with failed delisting. For batch deletion, the content related to main products may include: a) Total, used to record the number of main products to be deleted this time; b) Success, used to record the number of successfully deleted main products, supporting clicking "View" to jump to the "On Sale" tab page of the management page, default filtering out the successfully deleted main products, and unselecting after clicking "Reset"; c) Draft box, since there is no process of putting items into the draft box for batch deletion, it can be shown as "-"; d) Failure, used to record the number of main products with failed deletion. For batch deletion, the content related to sub-products may include: a) Total, used to record the number of sub-products to be deleted this time; b) Success, used to record the number of successfully deleted sub-products; c) Draft box, since there is no process of putting items into the draft box for batch deletion, it can be shown as "-"; d) Failure, used to record the number of sub-products with failed deletion. For batch modification, when the scope of batch product modification is selected as "Modify only main products" or "Modify main products and apply to all sub-products simultaneously", the modified quantity is shown. When "Modify sub-products" is selected, the main product can be shown as "-"; when the scope of batch product modification is selected as "Modify main products and apply to all sub-products simultaneously" or "Modify sub-products", the modified quantity is shown. When "Modify only main products" is selected, the sub-products can be shown as "-". Specifically, for batch modification, the content related to main products may include: a) Total, used to record the number of main products to be modified this time; b) Success, used to record the number of successfully modified main products, supporting clicking "View" to jump to the "On Sale" tab page of the management page, default filtering out the successfully modified main products, and unselecting after clicking "Reset"; c) Draft box, used to record the batch operation of saving failed modification orders to the draft box, supporting clicking "View" to jump to the draft box page, default filtering out these products, and unselecting after clicking "Reset". If only the price or inventory is modified, there will be no link to put items into the draft box, and it can be shown as 0; d) Failure, used to record the number of main products with failed modification. For batch modification, the content related to sub-products may include: a) Total, used to record the number of sub-products to be modified this time; b) Success, used to record the number of successfully modified sub-products; c) Draft box, since there is no process of putting items into the draft box for batch modification of sub-products, it can be shown as "-"; d) Failure, used to record the number of sub-products with failed modification. For batch export, since there is no change to product information, status, etc. for the export quantity, the corresponding columns for main products and sub-products can both be shown as "-".

[0166] In addition, the batch tool provided in the embodiments of the present application 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, multiple main products can be listed in batches, or sub-products corresponding to a certain main product or certain main products can be listed simultaneously. The specific operations may include: checking the main products -> batch listing -> selecting to list main products and sub-products simultaneously -> pop-up window confirmation. Or, when the main products have already been listed, only the sub-products corresponding to these main products can be listed in batches. For example, the main products are successfully listed, but the corresponding sub-products are not successfully listed. Therefore, a separate operation is required to "list all sub-products". The specific operations may include: checking the main products -> sub-product batch operation -> batch listing -> selecting the stores to be listed in the drawer -> clicking confirmation. Or, only multiple main products can be listed in batches without listing the sub-products. Or, multiple main products can be listed in batches, but only some of the sub-products corresponding to the stores are listed. For the case where the batch listing is successful, the sub-products are sold normally; for the case where the batch listing fails, the user can download the failure reason (such as abnormal store status), and after solving the failure reason, list them again.

[0168] For the above-mentioned batch delisting tool, multiple main products can be delisted in batches, and all corresponding sub-products are also delisted simultaneously. The specific operations may include: checking the main products -> main product batch operation -> batch delisting -> pop-up window confirmation. Or, the sub-products corresponding to multiple main products in some stores can be delisted in batches (for example, due to some regional supply chain problems, the sub-products in the stores in this region are temporarily delisted and may be listed again later). The specific operations may include: checking the main products -> sub-product batch operation -> batch delisting -> selecting the stores to be delisted in the drawer -> clicking confirmation. For the case where the batch delisting is successful, there is no other operation. For the case where the batch delisting fails, the user can download the failure reason, and after solving the failure reason, delist them again.

[0169] For the above-mentioned batch deletion tool, multiple main products can be deleted in batches, and all corresponding sub-products are also deleted simultaneously. The specific operations may include: checking the main products -> main product batch operation -> batch deletion -> pop-up window confirmation. Or, the sub-products corresponding to multiple main products in some stores can be deleted in batches (for example, due to some regional supply chain problems, the product is no longer sold and is directly deleted, that is, the distribution of the sub-products corresponding to the main product in this store is cancelled). The specific operations may include: checking the main products -> sub-product batch operation -> batch deletion -> selecting the stores to be deleted in the drawer -> clicking confirmation. For the case where the batch deletion is successful, there is no other operation. For the case where the batch deletion fails, the user can download the failure reason, and after solving the failure reason, delete them again.

[0170] Such asFigure 8 As shown in the figure, the batch tools developed on the management page in the embodiments of the present application can at least include: batch product placement, batch modification, batch listing, batch delisting, batch deletion, batch export, and batch operation records, so as to provide convenience for users to manage products in batches on the online sales platform in the instant retail scenario (especially in the scenario where a large number of large chain enterprises enter the instant retail scenario), greatly improving the efficiency of users' batch management of products, and at the same time improving the user experience of using the work website with this 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 some target sub-entities in the target entity, a first batch tool is provided on the management page of the target entity. The user only needs to perform a first configuration operation on the first batch tool to quickly implement this need, that is, the user, by using the first batch tool once, based on the target sub-entities and the target main object determined by this use of the first batch tool, batch operates on the target sub-objects corresponding to the target main object in the target sub-entities, so that the management pages of the target sub-entities display the target sub-objects belonging to the target sub-entities and corresponding to the target main object, without the user having to operate on the target main object and the target sub-objects one by one based on the identifiers of different objects within the chain entity, overcoming the problem of poor processing efficiency caused by the inability to batch process objects in the current chain entity, improving the processing efficiency of objects in the chain entity, and thus bringing convenience to the staff of the chain entity in the instant retail scenario.

[0172] Correspondingly, the embodiments of the present application further provide a batch processing device 900, as Figure 9 shown in the figure. The device 900 may include:

[0173] A first determination unit 901, configured to determine a target sub-entity and a target main object in response to a first configuration operation on a first batch tool on the management page of the target entity, where the target sub-entity is a lower-level entity of the target entity, the target main object is an object in the target entity, and the first batch tool is used to batch set the main object in the entity to the sub-entity;

[0174] A first display unit 902, configured to display, on the management pages of the target sub-entities, the target sub-objects corresponding to the target main object in the target sub-entity, where the target sub-objects have the same attribute information as the corresponding target main object.

[0175] In a possible implementation, on the first batch tool on the management page of the target entity, there is a first control for triggering the selection of the main object and a second control for triggering the selection of the sub-entity. 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, on the first batch tool on the management page of the target entity, there is a first control for triggering the selection of the main object and a third control for triggering the 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 it to all sub-entities of the target entity, and the target sub-entities are all sub-entities included in the target entity;

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

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

[0179] In response to the first configuration operation, generate a first main task for instructing the sub-object corresponding to the target main object to take effect in the target sub-entity;

[0180] The device 900 further includes:

[0181] A splitting unit, configured to split the first main task into N sub-tasks based on a task model of three levels or more. Each sub-task in the N sub-tasks is used to instruct the target sub-object corresponding to the target main object to take effect in the corresponding target sub-entity, and N is equal to the number of target sub-entities;

[0182] A statistics unit, configured to statistics the execution status of the N sub-tasks when the execution time of the first main task reaches a preset period.

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

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

[0185] A second display unit, 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 information on attributes to be modified.

[0186] In a 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 the configuration of information on attributes to be modified, the type of the object to be modified, and the scope of the object to be modified, a seventh control for triggering the download of a template file, and an eighth control for triggering the upload of a template file. The second determination unit is specifically configured to:

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

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

[0189] In response to operating the eighth control, obtain a fourth template file, where the fourth template file is a file after filling in the identifier of the object to be modified and the values of the information on attributes to be modified in the third template file;

[0190] Determine the identifier of the object to be modified and the information on attributes to be modified according to the fourth template file.

[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, display, on the management page of the target entity, the attribute information of the main object to be modified as the attribute information after being modified based on the information on attributes to be modified, and display, on the management page of a sub-entity belonging to the target entity, the attribute information of the sub-object of the main object to be modified in this sub-entity as the attribute information after being modified based on the information on attributes to be modified;

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

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

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

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

[0197] A download unit, configured to, in response to an operation on the ninth control, download an export file corresponding to the export task, where the export file includes values of preset export fields for each object to be exported.

[0198] In a 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 main 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 the export task. The third configuration operation includes 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.

[0199] In a possible implementation,

[0200] The management page of the target entity further 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: 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 a possible implementation,

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

[0203] It should be noted that for the specific implementation manner and achieved technical effects of the apparatus 900, reference may be made to Figure 1 the relevant descriptions of the method shown.

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

[0205] SeeFigure 10 , which shows a schematic structural diagram of an electronic device 1000 suitable for implementing the embodiments of the present disclosure. 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 (such as in-vehicle navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 10 The electronic device shown is merely an example and should not impose any limitations on the functions and usage scope of the embodiments of the present disclosure.

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

[0207] Generally, 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 wiredly to exchange data. Although Figure 10 the electronic device 1000 with various devices is shown, it should be understood that it is not required to implement or have all the shown devices. More or fewer devices may be alternatively implemented or had.

[0208] Specifically, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, the embodiments of the present disclosure include a computer program product, which includes a computer program carried on a non-transitory computer-readable medium, and the computer program includes program codes for performing the methods shown in the flowcharts. In such an embodiment, the computer program may 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 methods of the embodiments of the present disclosure are executed.

[0209] The electronic device provided by an embodiment of the present disclosure and the method provided by the above embodiment belong to the same inventive concept. For technical details not described in detail in this embodiment, reference may be made to the above embodiment, and this embodiment has the same beneficial effects as the above embodiment.

[0210] An embodiment of the present application further provides a computer-readable medium, in which instructions or a computer program are stored. When the instructions or the computer program run on a device, the device is caused to execute any implementation manner of the method provided by the embodiment of the present application.

[0211] It should be noted that the above computer-readable medium in the present disclosure may be a computer-readable signal medium, a computer-readable storage medium, or any combination of the two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having 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, the computer-readable storage medium may be any tangible medium that contains or stores a program, and the program can be used by or in combination with an instruction execution system, apparatus, or device. In the present disclosure, the computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, in which computer-readable program code is carried. Such a propagated data signal may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. The computer-readable signal medium may also be any computer-readable medium other than the computer-readable storage medium, and the computer-readable signal medium can send, propagate, or transmit a program for use by or in combination with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted by any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0212] In some embodiments, the client and the server can communicate using any currently known or future-developed network protocol such as HTTP (Hyper Text Transfer Protocol), and can be interconnected with digital data communication in any form or medium (e.g., a communication network). Examples of communication networks include local area networks ("LANs"), wide area networks ("WANs"), the Internet (e.g., the Internet), and end-to-end networks (e.g., ad hoc end-to-end networks), as well as any currently known or future-developed networks.

[0213] The above computer-readable medium can be included in the above electronic device; or can exist separately without being assembled into the electronic device.

[0214] The above computer-readable medium carries one or more programs, and when the one or more programs are executed by the electronic device, the electronic device can execute the above method.

[0215] Computer program code for performing the operations of the present disclosure can be written in one or more programming languages or combinations thereof. The programming languages include, but are not limited to, object-oriented programming languages such as Java, Smalltalk, C++, and also include conventional procedural programming languages such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, executed as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer can 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 can be connected to an external computer (e.g., by using an Internet service provider to connect through the Internet).

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

[0217] The units involved in the embodiments described in the present disclosure can be implemented in software or in hardware. Among them, the name of the unit / module does not, in some cases, constitute a limitation on the unit itself.

[0218] The functions described above in this document can be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that can be used include: Field Programmable Gate Arrays (FPGA), Application Specific Integrated Circuits (ASIC), Application Specific Standard Products (ASSP), System on a Chip (SOC), Complex Programmable Logic Devices (CPLD), and so on.

[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 connection with an instruction execution system, apparatus, or device. 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, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, 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 Disc 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 embodiments in this specification are described in a progressive manner. Each embodiment focuses on the differences from other embodiments. For the same or similar parts among the embodiments, reference can be made to each other. For the systems or devices disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the description is relatively simple. For related parts, reference can be made to the description in the method section.

[0221] It should be understood that in this application, "at least one (item)" means one or more, and "a plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships can exist. For example, "A and / or B" can mean: only A exists, only B exists, and both A and B exist at the same time. Among them, A and B can be singular or plural. The character " / " generally means that the associated objects before and after are in an "or" relationship. "At least one (one) of the following" or its similar expressions refer to any combination of these items, including any combination of single item (one) or plural items (ones). For example, at least one (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, and c can be single or multiple.

[0222] It should also be noted that in this article, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not expressly listed, or elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "including a..." does not exclude the existence of additional identical elements in the process, method, article or device including the said element.

[0223] The steps of the methods or algorithms described in combination with the embodiments disclosed in this article can be directly implemented by hardware, software modules executed by a processor, or a combination of both. The software module can be placed in a random access memory (RAM), memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, register, hard disk, removable disk, CD-ROM, or any other form of storage medium well-known in the technical field.

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

[0225] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be obvious to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to these embodiments shown herein, but rather to the broadest scope consistent with the principles and novel features disclosed herein.

Claims

1. A batch processing method, characterized in that, Including: In response to a first configuration operation on a first batch tool on the management page of a target entity, determining a target sub-entity and a target main object, where 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 into the sub-entities; On the management pages of the respective target sub-entities, displaying target sub-objects in the target sub-entities corresponding to the target main object, where the target sub-objects have the same attribute information as the corresponding target main objects.

2. The method according to claim 1, characterized in that, On the first batch tool on the management page of the target entity, there is a first control for triggering the selection of the main object and a second control for triggering the selection of the 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, on the first batch tool on the management page of the target entity, there is a first control for triggering the selection of the main object and a third control for triggering application to all sub-entities, 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 third control to apply to all sub-entities of the target entity, where the target sub-entities are all sub-entities included in the target entity; And / or, on the first batch tool on the management page of the target entity, there is a fourth control for triggering the download of a template file and a fifth control for triggering the upload of a template file, and 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, where the second template file is a file obtained by filling in the identifiers of the target main object and the target sub-entity in the first template file.

3. The method according to claim 1 or 2, characterized in that, The determining the target sub-entity and the target main object in response to the first configuration operation on the first batch tool on the management page of the target entity includes: In response to the first configuration operation, generating a first main task for instructing the sub-objects corresponding to the target main object to take effect in the target sub-entity; The method further includes: Based on a three-level or higher task model, splitting the first main task into N sub-tasks, where each of the N sub-tasks is used to instruct the target sub-objects corresponding to the target main object to take effect 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, counting the execution status of the N sub-tasks.

4. The method according to any one of claims 1-3, characterized in that, The method further includes: In response to a second configuration operation on a 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, where 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 the main object and / or the sub-object; On the management page of the target entity, displaying the attribute information of the object to be modified after being modified based on the attribute information to be modified.

5. The method according to claim 4, wherein On the second batch tool of the management page of the target entity, there is included at least one of the following controls: a sixth control for triggering the configuration of the attribute information to be modified, the type of the object to be modified, and the scope of the object to be modified, a seventh control for triggering the download of a template file, and an eighth control for triggering the upload of a template file. Responding to a second configuration operation on the second batch tool of the management page of the target entity to determine the identifier of the object to be modified and the attribute information to be modified includes: Responding to the operation of the sixth control, display a third template file; Responding to the operation of the seventh control, download the third template file; Responding to the operation of the eighth control, obtain a fourth template file, where the fourth template file is a file after filling in the values of the identifier of the object to be modified and the attribute information to be modified in the third template file; Determine the identifier of the object to be modified and the attribute information to be modified according to the fourth template file.

6. The method according to claim 4 or 5, characterized in that, On the management page of the target entity, displaying 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 the main object, on the management page of the target entity, display the attribute information of the main object to be modified 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, display the attribute information of the sub-object of the main object to be modified in this sub-entity 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, on the management page of the sub-entity belonging to the target entity, display the price or inventory of the sub-object of the main object to be modified in this sub-entity as the price or inventory modified based on the attribute information to be modified.

7. The method according to any one of claims 1-6, characterized in that, The method further includes: Responding to a third configuration operation on the third batch tool of the management page of the target entity, display the export progress of the corresponding export task on the batch operation record page; Responding to the completion of the export task for the object to be exported, display a ninth control for downloading the result of the export task on the batch operation record page; Responding to the operation of the ninth control, download the export file corresponding to the export task, where the export file includes the values of the preset export fields for each object to be exported.

8. The method according to claim 7, wherein On the third batch tool of the management page of the target entity, there is included 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 the object to be exported, and a thirteenth control for triggering the export. The third configuration operation includes 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 the object to be exported, and operating the thirteenth control to trigger the export task.

9. The method according to any one of claims 1 - 8, wherein The management page of the target entity further 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: batch operators, details of batch operations, 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-9, characterized in that The management page of the target entity further 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, characterized in that, including: A first determination unit, configured to determine a target sub-entity and a target main object in response to a first configuration operation on a first batch tool on the management page of the target entity, where 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 into the sub-entity; A first display unit, configured to display, on the management page of each of the target sub-entities, a target sub-object corresponding to the target main object in the target sub-entity, where the target sub-object has the same attribute information as the corresponding target main object.

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

13. A readable medium, characterized in that, Instructions or programs are stored in the readable medium, and when the instructions or programs run on the processor, the processor is caused to execute the method according to any one of claims 1-10.

Images