Invoice generation method and device therefor

Abstract

An invoice generation method and a device therefor are provided. The method comprises the steps of: receiving identification information about the invoice from a user device; generating a script for outputting the invoice corresponding to the identification information; and transmitting the script to the user device.

Description

Method for creating an invoice and device therefor

[0001] The present disclosure relates to a method for generating an invoice and a device therefor. Specifically, the present disclosure relates to a method for reducing the load on a client by generating an invoice image on a server.

[0002] When a customer orders a product, a worker at a pack station must package the product and attach an invoice. In the process of issuing an invoice, when a worker requests an invoice through a client, the request is passed through an invoice server and then to a printing program included in the client. A request for data for generating an invoice image is then sent back to the invoice server through the printing program. The invoice image is then rendered on the client using the data obtained from the invoice server and then sent to an output device for printing.

[0003] The numerous sequences required to issue an invoice increase network delay / latency and increase the load on the client rendering the invoice image. Furthermore, the process of transmitting the rendered invoice image to the output device requires converting the invoice image into a format suitable for printing, which can increase the client load and reduce output speed.

[0004] Therefore, a new invoice creation method is required to solve these problems in the process of issuing invoices.

[0005] The technical problem to be solved through the embodiments of the present disclosure is to provide a method for generating an invoice image in an invoice server to reduce the processor / memory load of a client, and a computing device for performing the method.

[0006] The technical problem to be solved through the embodiments of the present disclosure is to provide a method for simplifying the flow of an invoice issuance procedure by reducing many legacy systems used in the invoice issuance procedure, and a computing device for performing the method.

[0007] Another technical problem to be solved through embodiments of the present disclosure is to provide a method for generating an invoice image using ZPL (Zebra Programming Language) and a computing device for performing the method in order to reduce network delay / latency occurring in the process of generating an invoice.

[0008] The technical problems to be solved by the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the art related to the present disclosure based on the detailed description below.

[0009] According to an embodiment of the present disclosure, a method for generating an invoice, performed by a computing device, is provided. The method may include the steps of receiving identification information of an invoice from a user device, generating a script for outputting the invoice corresponding to the identification information, and transmitting the script to the user device.

[0010] In one embodiment of the present disclosure, the script may be written in ZPL (Zebra Programming Language).

[0011] In one embodiment of the present disclosure, the step of generating the script may include the step of generating a first script for setting an output format of the invoice and the step of generating a second script for outputting invoice data corresponding to the identification information, and the script may include the first script and the second script.

[0012] In one embodiment of the present disclosure, the method may further include a step of receiving setting information for the output format from the user device, and the first script may be for setting the output format corresponding to the setting information.

[0013] In one embodiment of the present disclosure, the method may further include a step of receiving output status information indicating whether output of the script is successful or not from the user device after transmitting the script to the user device.

[0014] According to an embodiment of the present disclosure, an invoice generation device is provided. The device includes at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the at least one processor to perform operations, wherein the operations may include receiving identification information of an invoice from a user device, generating a script for outputting the invoice corresponding to the identification information, and transmitting the script to the user device.

[0015] In one embodiment of the present disclosure, the script may be written in ZPL (Zebra Programming Language).

[0016] In one embodiment of the present disclosure, the operation of generating the script may include an operation of generating a first script for setting an output format of the invoice and an operation of generating a second script for outputting invoice data corresponding to the identification information, and the script may include the first script and the second script.

[0017] In one embodiment of the present disclosure, the operations may further include an operation of receiving setting information for the output format from the user device, and the first script may be for setting the output format corresponding to the setting information.

[0018] In one embodiment of the present disclosure, the operations may further include an operation of receiving output status information indicating whether output of the script is successful or not from the user device after transmitting the script to the user device.

[0019] The above-described problem solving means are only some of the examples of the present disclosure, and various examples reflecting the technical features of the present disclosure can be clearly understood by a person having ordinary skill in the art related to the present disclosure based on the detailed description below.

[0020] FIG. 1 is a configuration diagram of an invoice issuance system according to one embodiment of the present disclosure.

[0021] FIG. 2 illustrates the overall operation flow of an invoice issuance system according to one embodiment of the present disclosure.

[0022] FIG. 3 is a flowchart illustrating an example of an invoice generation method according to one embodiment of the present disclosure.

[0023] FIG. 4 is a flowchart illustrating a specific example of a script generation method according to some embodiments of the present disclosure.

[0024] FIGS. 5 and 6 illustrate examples of scripts generated according to some embodiments of the present disclosure.

[0025] FIG. 7 illustrates an example of an invoice image generated according to some embodiments of the present disclosure.

[0026] FIG. 8 illustrates an example of a screen displaying the output status of an invoice according to some embodiments of the present disclosure.

[0027] FIG. 9 illustrates an example of a screen for setting an output format of an invoice according to some embodiments of the present disclosure.

[0028] FIG. 10 illustrates an example of a screen for generating a script according to some embodiments of the present disclosure.

[0029] FIG. 11 is a block diagram illustrating an example of a computing device for performing some embodiments of the present disclosure.

[0030] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the attached drawings. The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described in detail below together with the attached drawings. However, the present disclosure is not limited to the embodiments described below and may be implemented in various different forms. These embodiments are provided only to ensure that the present disclosure is complete and to fully inform those skilled in the art of the present disclosure of the scope of the invention, and the embodiments of the present disclosure are defined only by the scope of the claims.

[0031] To avoid ambiguity in the concepts of this disclosure, the known components may be omitted or illustrated in block diagram form focusing on the core functions of each component. Throughout this disclosure, identical components are described using the same reference numerals, even if they appear on different drawings.

[0032] Unless otherwise defined, all terms (including technical and scientific terms) used herein may be used in the same sense as commonly understood by those of ordinary skill in the art to which this disclosure pertains. Furthermore, terms defined in commonly used dictionaries are not to be interpreted ideally or excessively unless explicitly and specifically defined otherwise. The terminology used herein is for the purpose of describing embodiments and is not intended to limit the present invention. In this disclosure, singular forms also include plural forms, unless specifically stated otherwise.

[0033] In addition, the terminology used in this disclosure is only used to describe specific embodiments, and is not intended to limit the features, components, order, etc. described in the specification. The terms "comprises" and / or "comprising" used in this disclosure express the presence of features, components, steps, operations, and / or combinations thereof described in the specification, but do not exclude the presence or addition of one or more other features, components, steps, operations, and / or combinations thereof.

[0034] Additionally, terms such as first, second, A, B, (a), (b), etc. used in the following embodiments are only used to distinguish certain components from other components, and the nature, order, or sequence of the components are not limited by the terms. For example, without departing from the scope of the present disclosure, the first component may be referred to as the second component, and similarly, the second component may be referred to as the first component.

[0035] Additionally, in this disclosure, " / " and "," should be interpreted as indicating "and / or". For example, "A / B" and "A, B" may mean "A and / or B".

[0036] This disclosure proposes a method for generating an invoice image. Specifically, the disclosure proposes a method for generating an invoice image by an invoice server upon receiving an invoice generation request from a client.

[0037] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings.

[0038] FIG. 1 is a configuration diagram of an invoice issuance system according to one embodiment of the present disclosure.

[0039] The invoice issuing system of FIG. 1 may provide a framework for performing methods and / or operations according to some embodiments of the present disclosure. For example, the invoice issuing system may refer to a system that implements a platform for generating an invoice image and generating / outputting the generated invoice image according to some embodiments of the present disclosure.

[0040] Referring to FIG. 1, the invoice issuing system may include a user device (100), an invoice generation device (200), and / or a database (300).

[0041] The user device (100) may include various devices that the user uses to communicate and transmit various data and / or information with other devices.

[0042] The user device (100) may include, but is not limited to, a smartphone, a tablet PC, a laptop, etc. For example, the user device (100) may include various computing devices equipped with wireless communication means and / or computing means. For another example, the user device (100) may include a product packaging device (also referred to as an auto bag), an output device (e.g., a labeler, a printer, etc.) that outputs an invoice generated according to some embodiments of the present disclosure. In the present disclosure, all computing devices used by a user to receive an invoice, including a smartphone, a tablet PC, a laptop, a product packaging device, and an output device, are referred to as user devices (100). In addition, the user device (100) may be referred to as a user terminal, a wireless device, a mobile terminal, a portable device, etc.

[0043] A user of the present disclosure may refer to a worker requesting invoice issuance according to some embodiments of the present disclosure. For example, the user may request invoice issuance via a first user device and output an invoice image generated by an invoice generation device (200) via a second user device. In another example, the user may directly write a script for generating an invoice image via the first user device and output an invoice image in script format via the second user device.

[0044] According to some embodiments of the present disclosure, the user device (100) may transmit a request for invoice generation along with identification information for the invoice to be generated to the invoice generation device (200). For example, the identification information for the invoice may be an identification number of the invoice. Specifically, the user device (100) may transmit a request for invoice data and / or an invoice image for invoice generation to the invoice generation device (200) in response to a user input requesting the issuance of an invoice corresponding to a customer's order.

[0045] The user device (100) may receive an invoice image generated from an invoice generation device (200) according to some embodiments of the present disclosure, transmit the invoice image to another user device, or output the invoice image.

[0046] Additionally, the user device (100) may transmit setting information regarding the output format of the invoice image to the invoice generation device (200). For example, the user may set an option regarding the output format of the invoice image through the user device (100), and the user device (100) may transmit the setting information set by the user to the invoice generation device (200) in response to a user input regarding the setting. In this case, the invoice generation device (200) may generate a script for generating / outputting the invoice image based on the received setting information.

[0047] Additionally, the user device (100) may transmit setting information regarding the output format of the invoice image to another user device for outputting the invoice. For example, the user device (100) may transmit setting information set by the user to another output device for outputting an invoice image generated by the invoice generation device (200) based on user input that sets an option regarding the output format of the invoice image.

[0048] For example, options for the output format of an invoice image that a user can set may include the location at which the invoice data is displayed on the invoice image, the font, size, color, etc., but are not limited to the examples listed. For example, options for the output format of an invoice image may include settings for an output device, such as resolution (e.g., DPI (Dots Per Inch)), font extension, output page orientation, output paper orientation, compression format, and text / image output format.

[0049] The user device (100) may include at least one computer program implementing the functions of the invoice issuing system. In other words, the user device (100) may include at least one memory for loading at least one computer program implementing the functions of the invoice issuing system, and at least one storage for storing at least one computer program. For example, the user device (100) may include a first program for receiving a request for invoice issuance from a user, and a second program for transmitting a request for invoice data and / or an invoice image to the invoice generation device (200) in response to the user input.

[0050] Additionally, the user device (100) may, in response to user input for a script for generating an invoice image, transmit the script to another user device for printing an invoice or print an invoice image.

[0051] The user device (100) may display a user interface implementing functions of an invoice issuance system according to some embodiments of the present disclosure. For example, the user device (100) may display a screen for displaying the output status of an invoice, managing the output status, setting the output format of the invoice, generating a script, and the like.

[0052] Hereinafter, a user device (100) that transmits a request for invoice creation to an invoice creation device (200) is referred to as a client, and an invoice creation device (200) that receives a request for invoice creation from a client and provides data for invoice creation (e.g., output format, invoice data, invoice image, etc.) may be referred to as an invoice server.

[0053] The invoice generation device (200) may perform operations for generating invoices according to some embodiments of the present disclosure using data for generating invoices included in the database (300). For example, when the invoice generation device (200) receives a request for generating an invoice from a client along with invoice identification information, the device may generate an invoice image using data corresponding to the received invoice identification information among the data included in the database (300).

[0054] The operation of the invoice generation device (200) may be performed by at least one computing device. For example, all functions of the invoice generation device (200) may be implemented on a single computing device. In another example, some functions of the invoice generation device (200) may be implemented on a first computing device, and the remaining functions may be implemented on a second computing device. Furthermore, specific functions of the invoice generation device (200) may be implemented on one or more computing devices.

[0055] The database (300) may include data necessary for generating an invoice. For example, the database (300) may include an invoice output format, invoice data, etc. The invoice output format may include information regarding the location, font, size, color, etc., at which the invoice data is displayed on the invoice image. The invoice data may include an order number, an invoice identification number, a logistics / delivery center name corresponding to the order, product information (e.g., product name, seller information), buyer information (e.g., name, address, etc.), delivery information (e.g., a buyer's delivery request message, etc.), etc.

[0056] The components illustrated in FIG. 1 can communicate via various types of wired / wireless networks. The device and / or system according to the present disclosure can be applied to a local area network (LAN), a wide area network (WAN), a mobile radio communication network, Wibro (Wireless Broadband Internet), etc., and is not limited thereto, and can also be applied to any other communication system.

[0057] Referring to FIGS. 2 to 10 below, embodiments of an invoice issuing system issuing invoices according to embodiments of the present disclosure will be described in detail.

[0058] First, the overall operation flow of the invoice issuance system according to one embodiment of the present disclosure will be described with reference to FIG. 2.

[0059] Referring to FIG. 2, the client (10) can receive a user input requesting an invoice issuance through a warehouse management program (11) running on a web browser, and in response to the user input, can transmit an invoice creation request to an invoice creation device (200) through an extension program (12) (S1, S2).

[0060] The extension program (12) is a web browser extension program that supports modification of the web browser on which the warehouse management program (11) is executed. The extension program (12) can be executed on all web browsers regardless of the type of operating system (OS) and can support compatibility between computing devices using different OSs. For example, even if the OS of the client (10) and the OS of the output device (20) are different, the extension program (12) can be operated for issuing invoices according to some implementations of the present disclosure, such as transmitting and receiving data and / or information for generating and / or printing invoices.

[0061] The user interface implemented by the warehouse management program (11) and / or the extension program (12) is described below with reference to FIGS. 8 to 10.

[0062] When a user requests invoice issuance through a warehouse management program (11) supported by a warehouse management system, the request for invoice creation can be transmitted from the client (10) to the invoice creation device (200), which is the invoice server, through an extension program (12) without having to go through another system to transmit the invoice creation request to the invoice server (S1, S2), thereby simplifying the process flow for invoice issuance. Accordingly, network delay / latency can be reduced.

[0063] Here, the warehouse management program (11) can correspond to the first program described in Fig. 1, and the extension program (12) can correspond to the second program described in Fig. 1.

[0064] In S2, the client (10) can, in response to a user input setting an option for the output format of the invoice image, transmit setting information for the output format set by the user to the invoice generation device (200) via the extension program (12). A specific embodiment of this will be described later with reference to FIG. 9.

[0065] An invoice generation device (200) that receives an invoice generation request from a client (10) can generate an invoice image and transmit the generated invoice image to the client (10) via an extension program (12) (S3).

[0066] The client (10) can transmit the invoice image received from the invoice generation device (200) to the output device (20) to output it (S4).

[0067] Additionally, the client (10) may receive the output status of the invoice image from the output device (20) after transmitting the invoice image to the output device (20) (S4). Here, the output status may include whether the output is complete or whether the output has failed.

[0068] In addition, the client (10) that receives the invoice image from the invoice generation device (200) may transmit the output status received from the output device (20) to the invoice generation device (200), which is an invoice server, through the extension program (12). In other words, after transmitting the invoice image to the client (10), the invoice generation device (200) may receive the output status from the client (10) in order to update the invoice generation / output operation, such as modifying the transmitted invoice image, regenerating the transmitted invoice image, or generating another invoice image later.

[0069] Meanwhile, although FIG. 2 illustrates a case where an invoice image is generated by an invoice generation device (200), the present invention is not limited thereto. For example, a user may directly write a script for generating / outputting an invoice image using a client (10), and the client (10) may receive user input for the script and transmit the script to an output device (20) in response to the user input. A specific embodiment of this will be described below together with the description of FIG. 10.

[0070] The client (10) and / or the output device (20) may correspond to the user device (100) of FIG. 1, and although FIG. 2 illustrates the client (10) and the output device (20) as separate objects, this is an example and is not limited thereto. The client (10) and the output device (20) may be the same object.

[0071] Hereinafter, with reference to FIGS. 3 and 4, a method for generating an invoice by an invoice generating device (200) according to some embodiments of the present disclosure will be specifically described.

[0072] For reference, FIGS. 3 and 4 illustrate steps / operations performed in the invoice generation device (200) of FIG. 1. Therefore, in the following description, if the subject of a specific step / operation is omitted, it can be understood that the step / operation is performed in the invoice generation device (200) of FIG. 1.

[0073] FIG. 3 is a flowchart illustrating an example of an invoice generation method according to an embodiment of the present disclosure. S100 to S300 of FIG. 3 may correspond to S2 to S3 of FIG. 2.

[0074] Referring to FIG. 3, invoice identification information may be received from a user device (S100). Here, the invoice identification information may refer to an invoice identification number generated in response to an order.

[0075] Next, a script for outputting an invoice corresponding to the identification information may be generated (S200), and the script generated in S200 may be transmitted to a user device (S300). For example, in S200, the script may be written in ZPL (Zebra Programming Language).

[0076] In S100 and S300, the user device can correspond to the client (10) of FIG. 2, and although not shown in FIG. 3, the user device can transmit an invoice image generated from the invoice generation device (200) to the output device (20) as described with reference to FIG. 2.

[0077] Generating an invoice image on the invoice server may involve both generating the invoice image in a graphical format (i.e., directly generating an image file representing the invoice) and generating a script to generate / output the invoice image. For example, if the invoice image is generated in a script format (e.g., ZPL script format), the network delay / latency may be reduced compared to generating the invoice image in a graphical format, because the output device can parse the script to output the invoice image without generating an image file in the graphical format.

[0078] Furthermore, the invoice generation device (200) can optimize caching when generating and transmitting invoice images, thereby reducing load and maintaining constant processor / memory usage. In the following descriptions, generating an invoice image will be understood as generating a script for generating / outputting the invoice image.

[0079] Next, a method for generating a script according to some embodiments of the present disclosure will be described with reference to FIG. 4.

[0080] Specifically, FIG. 4 is a flowchart illustrating a specific example of S200 of FIG. 3. S100 to S300 of FIG. 4 may correspond to S100 to S300 of FIG. 3.

[0081] Referring to FIG. 4, a first script for setting an invoice output format in S200 may be generated (S201), and a second script for outputting invoice data corresponding to the identification information received in S100 may be generated (S202). The script generated in S200 may include both the first script and the second script. Specific examples of the script generated in S200 will be described below with reference to FIGS. 5 and 6.

[0082] Additionally, configuration information regarding the output format of the invoice may be received from the user device before generating the script (S110). In this case, the first script generated in S201 may be a script for setting the output format in response to the configuration information received in S110. In other words, the invoice generation device (200) may receive configuration information regarding the output format of the invoice image from the client (10) and generate the invoice image based on the received configuration information. For reference, although FIG. 4 illustrates S100 and S110 sequentially, they may be performed simultaneously.

[0083] For example, a user can set an option for the output format of an invoice image through the user device (100) of FIG. 1, and the user device (100) can transmit the setting information set by the user to the invoice generation device (200) in response to a user input for the setting.

[0084] In S110, the setting information for the output format may include setting information for the location, font, size, and / or color at which the invoice data is displayed on the invoice image, and may also include setting information for setting options of the output device, such as the resolution of the invoice image (e.g., DPI (Dot Per Inch)), font extension, output page orientation, output paper orientation, compression format, and / or text / image output format. A specific example of this will be described below with reference to FIG. 9.

[0085] In addition, although not shown in FIGS. 3 and 4, as described with reference to FIG. 2, the invoice generation device (200) can receive output status information indicating whether output of the script transmitted from S300 was successful from the user device, and can store the received output status information in the database (300) of FIG. 1.

[0086] Next, an embodiment of a method for generating a script for generating / outputting an invoice image is described with reference to FIGS. 5 and 6.

[0087] Specifically, FIG. 5 illustrates an example of a script generated to output a logistics / delivery center name according to some embodiments of the present disclosure.

[0088] The first script (500-1) is a script for generating / outputting an invoice image in graphic format and can set the output format of the invoice data included in the second script (500-2). The second script (500-2) is a script for generating / outputting an invoice image in graphic format and is a script for outputting invoice data (e.g., a logistics / delivery center name).

[0089] The ZPL script (500-3) is a script for creating / outputting an invoice image in ZPL format, and the first script (500-1) and the second script (500-2) can be converted into the ZPL script (500-3) as shown in FIG. 5.

[0090] For example, 5a is a code pair corresponding to a letter shape, 5b is a code pair corresponding to a location where letters are to be displayed, 5c is a code pair corresponding to a letter size, and 5d is a code pair corresponding to a logistics / delivery center name. As shown in FIG. 5, the third script (500-3) can be generated by converting each code included in the first script (500-1) and the second script (500-2) into ZPL format.

[0091] For example, 5a of the ZPL script (500-3) may be created in such a way that the character shape corresponding to 5a of the first script (500-1) is assigned to the 'L' character. In addition, 5b of the ZPL script (500-3) may be created based on a calculated position value by applying scaling, rotation, etc. to correspond to a position set according to the X coordinate, Y coordinate, width value, and height value corresponding to 5b of the first script (500-1). In addition, 5c of the ZPL script (500-3) may be created based on a calculated value (e.g., a value calculated by multiplying the character size value corresponding to 5c of the first script (500-1) by 300 / 72) calculated by calculating the character size value corresponding to 5c of the first script (500-1) and a predetermined value (e.g., a DPI to be displayed / original DPI).

[0092] Additionally, FIG. 6 illustrates an example of a script generated to output an invoice barcode according to some embodiments of the present disclosure.

[0093] The first script (600-1) is a script for generating / outputting an invoice image in graphic format and can set the output format of the invoice data included in the second script (600-2). Specifically, the first script (600-1) is a script for setting the format for outputting the invoice identification information exemplified in the second script (600-2) in the form of a barcode. The second script (600-2) is a script for generating / outputting an invoice image in graphic format and is a script for outputting invoice data (e.g., invoice identification information).

[0094] The ZPL script (600-3) is a script for creating / outputting an invoice image in ZPL format, and the first script (600-1) and the second script (600-2) can be converted into the ZPL script (600-3) as shown in FIG. 6.

[0095] For example, 6a is a code pair corresponding to the position where the barcode is to be displayed, 6b is a code pair corresponding to the barcode width, 6c is a code pair corresponding to the barcode height, 6d is a code pair corresponding to the rotation angle of the barcode, and 6e is a code pair corresponding to the invoice identification information. As shown in FIG. 6, the ZPL script (600-3) can be generated by converting each code included in the first script (600-1) and the second script (600-2) into the ZPL format.

[0096] For example, 6a of the ZPL script (600-3) may be created based on the calculated position value by applying scaling, rotation, etc. to correspond to the position set according to the X coordinate, Y coordinate, width value, and height value corresponding to 6a of the first script (600-1). In addition, 6b of the ZPL script (600-3) may be created based on the calculated barcode width value (e.g., round (a value calculated by multiplying the barcode width value corresponding to 6b of the first script (600-1) by 300 / 72)) by calculating the barcode width value corresponding to 6b of the first script (600-1) and a predetermined value. In addition, the barcode height value corresponding to 6c of the first script (600-1) and a predetermined value are calculated and the barcode height value calculated by multiplying the barcode height value corresponding to 6c of the first script (600-1) by 10 and 300 / 72 may be used as the basis for writing the 6c of the ZPL script (600-3). For reference, the code '^BY6,3.0,271' written in ZPL as an example in FIG. 6 may mean '^BY barcode width, barcode width ratio, barcode height', and the barcode width ratio may be a preset value (e.g., a preset constant value). In addition, the 6d of the ZPL script (600-3) may be written in a manner in which the rotation angle value corresponding to 6d of the first script (600-1) is assigned to a specific character (e.g., the 'I' character assigned 270 degrees).

[0097] FIG. 7 illustrates an example of an invoice image generated according to some embodiments of the present disclosure.

[0098] Referring to FIG. 7, the invoice image may display an order number, an invoice identification number, a logistics / delivery center name (701) corresponding to the order, a barcode (702) for invoice identification, product information (e.g., product name, seller information), buyer information (e.g., name, address, etc.), delivery information (e.g., buyer's delivery request message, etc.), etc.

[0099] The logistics / delivery center name (701) illustrated in FIG. 7 illustrates a logistics / delivery center name printed based on the ZPL script (500-3) illustrated in FIG. 5, and the barcode (702) for invoice identification illustrates a barcode printed based on the ZPL script (600-3) illustrated in 600-3 of FIG. 6.

[0100] The functions of the invoice issuing system of FIG. 1, as described with reference to FIGS. 2 to 4, may be displayed using a graphical user interface. Hereinafter, some embodiments of the present disclosure related thereto will be described with reference to FIGS. 8 to 10.

[0101] Specifically, FIG. 8 illustrates an example of a screen displaying the output status of an invoice on a web browser in which the warehouse management program (11) and / or extension program (12) of the client (10) of FIG. 2 is executed.

[0102] Referring to Fig. 8, a user can access a screen where a function supported by the extension program (12) is implemented by clicking / selecting at least one icon button (801) displayed on the web browser screen illustrated in Fig. 8. At this time, the form of the displayed screen may be a full screen, a pop-up screen, etc.

[0103] For example, a user can click / select at least one icon button (801) to access a pop-up screen where the output status of an invoice as shown in FIG. 8 is displayed and the output status can be managed.

[0104] This screen may display an output device connected to the client (10), the connection status of the output device, a list of invoices (802) for which output has been requested, an output status (803) of each invoice, and / or an output progress status of each invoice. For example, as illustrated in FIG. 8, the list of invoices (802) may be displayed as a list of identification information of each invoice. In addition, the output progress status of each invoice may be displayed in the form of a progress bar. For another example, although not illustrated in FIG. 8, the output progress status of each invoice may be displayed in the form of text as a percentage value calculated according to the output progress.

[0105] The output status (803) may include whether the output is complete or whether the output failed. For example, if the output of an invoice is complete, the output status (803) may be displayed in text form, such as "Output Complete." For another example, if the invoice is being printed, the output status (803) may be displayed in text form, such as "Data Request." For another example, if the printing of an invoice is canceled, the output status (803) may be displayed in text form, such as "Output Canceled." In this case, the reason for the cancellation of the output may also be displayed on the screen. For example, as illustrated in FIG. 8, the screen may display a message related to the output status of each invoice, and if the printing is canceled, the reason for the cancellation of the output may be displayed in text form, such as "User Manual Cancellation," in the message field.

[0106] Additionally, as illustrated in FIG. 8, this screen may display a button for canceling a print request for all invoices included in the invoice list (802). Additionally, although not illustrated in FIG. 8, a button for canceling a print request for each invoice included in the invoice list (802) may be displayed.

[0107] Additionally, as illustrated in FIG. 8, the user can filter the invoice list (802) by output status on this screen and check the filtered list.

[0108] Additionally, as illustrated in FIG. 8, this screen may display a button for manually connecting an output device.

[0109] FIG. 9 illustrates an example of a screen for setting the output format of an invoice on a web browser in which the warehouse management program (11) and / or extension program (12) of the client (10) of FIG. 2 is executed.

[0110] This screen may display a user interface for setting options for the output device connected to the client (10), the target backend server, and the output format.

[0111] The target backend server may refer to an API (Application Programming Interface) endpoint of an invoice server (i.e., an invoice generation device (200)) that the warehouse management program (11) and / or extension program (12) wants to access to set the output format.

[0112] In this screen, the user can directly set the output format of the invoice image, customizing the settings for the output format included in the ZPL script generated by the invoice generation device (200) according to some embodiments of the present disclosure.

[0113] Options for the output format of the invoice image that can be set by the user through this screen may include, as illustrated in FIG. 9, options for the output format of the invoice image, such as resolution (e.g., DPI (Dots Per Inch)), font extension, output page orientation, output paper orientation, compression format, text / image output format, and setting options for the output device. However, the present invention is not limited to the examples listed. For example, although not illustrated in FIG. 9, options for the output format may include the location at which invoice data is displayed on the invoice image, font, size, color, and the like.

[0114] For example, as illustrated in FIG. 9, a user interface (e.g., a check box) may be displayed on this screen to indicate whether the setting options of the output device are set to default or have been set directly by the user, and the user may uncheck the check box and directly set / change the setting options of the output device.

[0115] Additionally, as illustrated in FIG. 9, the user can save the log recorded by the warehouse management program (11) and / or the extension program (12) through the user interface (e.g., button) displayed on this screen, or connect an output device that is not registered to the client (10).

[0116] Meanwhile, to access this screen and perform operations according to some embodiments of the present disclosure, such as setting the output format of an invoice image, saving a log file, or connecting an unregistered printer, a user may need to obtain a license to access the screen. That is, access rights may be restricted so that only authorized users can access the screen.

[0117] Fig. 10 illustrates an example of a screen for generating a script on a web browser in which a warehouse management program (11) and / or an extension program (12) of a client (10) is executed.

[0118] As shown in Fig. 10, a user can directly create a ZPL script for generating / outputting an invoice image. Additionally, a button for transmitting the ZPL script created by the user to an output device connected to the client (10) may be displayed on this screen.

[0119] Additionally, as illustrated in FIG. 10, the user can print a test page, install a font file to set the appearance of the letters included in the invoice, or execute a ZPL script on a URL (Uniform Resource Locator) through a user interface (e.g., a button) displayed on this screen.

[0120] Also, referring to FIGS. 9 and 10, a user can access the screens of FIG. 9 and 10 through the tab (901, 1001) function. For example, in response to a user input of selecting / clicking a first tab (901) on the same page, a portion of the entire screen of the page can be switched to a screen for setting an output format, as illustrated in FIG. 9, and in response to a user input of selecting / clicking a second tab (1001), a portion of the entire screen of the page can be switched to a screen for generating a script, as illustrated in FIG. 10.

[0121] FIG. 11 is a block diagram illustrating an example of a computing device for performing some embodiments of the present disclosure.

[0122] Referring to FIG. 11, a computing device (1) may include one or more processors (101), a bus (103), a communication interface (104), a memory (102) for loading a computer program executed by the processor (101), and a storage (105) for storing a computer program (106). However, only components related to the embodiment of the present disclosure are illustrated in FIG. 11. Therefore, a person skilled in the art to which the present disclosure pertains will appreciate that other general components may be included in addition to the components illustrated in FIG. 11. That is, the computing device (1) may further include various components in addition to the components illustrated in FIG. 11. In addition, in some cases, the computing device (1) may be configured in a form in which some of the components illustrated in FIG. 11 are omitted. Hereinafter, each component of the computing device (1) will be described.

[0123] The processor (101) can control the overall operation of each component of the computing device (1). The processor (101) can be configured to include at least one of a CPU (Central Processing Unit), an MPU (Micro Processor Unit), an MCU (Micro Controller Unit), a GPU (Graphics Processing Unit), or any other type of processor well known in the technical field of the present disclosure. In addition, the processor (101) can perform operations for at least one application or program for executing a method and / or operation according to embodiments of the present disclosure. The computing device (1) can be equipped with one or more processors.

[0124] In addition, the system and / or computing device (1) according to embodiments of the present disclosure may further include a database, and the processor (101) may store data and / or information generated / output according to some embodiments of the present disclosure in the memory (102) and / or the database. Here, the database in which the data and / or information is stored is not limited to a database within the system and / or computing device (1) according to the present disclosure, and may include, for example, a database of an external server.

[0125] The memory (102) can store various data, commands, and / or information. The memory (102) can load a computer program (106) from the storage (105) to execute methods and / or operations according to embodiments of the present disclosure. The memory (102) may be implemented as a volatile memory such as RAM, but the present disclosure is not limited thereto.

[0126] The bus (103) can provide a communication function between components of the computing device (1). The bus (103) can be implemented as various types of buses such as an address bus, a data bus, and a control bus.

[0127] The communication interface (104) can support wired / wireless Internet communication of the computing device (1). Furthermore, the communication interface (104) can also support various communication methods other than Internet communication. To this end, the communication interface (104) can be configured to include a communication module well known in the technical field of the present disclosure.

[0128] Storage (105) can non-temporarily store one or more computer programs (106). Storage (105) can be configured to include non-volatile memory such as Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, a hard disk, a removable disk, or any form of computer-readable recording medium well known in the art to which the present disclosure pertains.

[0129] The computer program (106) may include one or more instructions that, when loaded into the memory (102), cause the processor (101) to perform methods and / or operations according to various embodiments of the present disclosure. That is, the processor (101) may perform the methods / implementations / operations according to various embodiments of the present disclosure by executing the one or more loaded instructions.

[0130] In the present disclosure, a computer-readable (non-volatile) storage medium can store at least one instruction or computer program, which when executed by at least one processor can cause the at least one processor to perform a method and / or operation according to some embodiments of the present disclosure.

[0131] For example, the computer program (106) may receive identification information of an invoice from a user device, generate a script for generating / outputting the invoice corresponding to the identification information, and transmit the script to the user device.

[0132] According to some embodiments of the present disclosure, by generating an invoice image on a server that receives a request for invoice data, the client does not need to render the invoice image. This reduces the processor / memory load on the client, increases the speed of invoice generation / output, and reduces the time required to generate / output invoices.

[0133] Additionally, according to some embodiments of the present disclosure, since the invoice image is generated in a script format (e.g., a ZPL script format), the delay / latency that occurs during the process of generating the invoice image can be reduced compared to when the invoice image is generated in a graphical format, and thus the time required to print the invoice can be reduced.

[0134] Various embodiments of the present disclosure and effects according to the embodiments have been described with reference to FIGS. 1 to 11. The effects according to the technical concept of the present disclosure are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art from the contents of the present disclosure.

[0135] Although the components constituting the embodiments of the present disclosure have been described as being combined or operating in combination as one, the present disclosure is not necessarily limited to such embodiments. That is, within the scope of the present disclosure, the components may be selectively combined and operated in one or more combinations.

[0136] Although operations are depicted in the drawings in a specific order, this should not be construed as requiring that the operations be performed in the specific order depicted, or in a sequential order, or that all depicted operations be performed to achieve the desired results. In certain circumstances, multitasking and parallel processing may be advantageous. Furthermore, the separation of various components in the embodiments described above should not be construed as requiring such separation, and it should be understood that the program components and systems described may generally be integrated together into a single software product or packaged into multiple software products.

[0137] Although the embodiments of the present disclosure have been described with reference to the attached drawings, those skilled in the art will appreciate that the present disclosure can be implemented in other specific forms without altering the technical spirit or essential features thereof. Therefore, it should be understood that the embodiments described above are exemplary in all respects and not restrictive. The scope of protection of the present disclosure should be interpreted by the claims below, and all technical ideas within a scope equivalent thereto should be interpreted as being included within the scope of the rights of the present disclosure.

Claims

1. In a method for generating an invoice performed by a computing device, A step of receiving identification information of an invoice from a user device; A step of generating a script for outputting the invoice corresponding to the above identification information; and comprising the step of transmitting the script to the user device; How to create an invoice.

2. In paragraph 1, The above script is written in ZPL (Zebra Programming Language). How to create an invoice.

3. In paragraph 1, The steps to create the above script are: A step of generating a first script for setting the output format of the above invoice; and A step of generating a second script for outputting invoice data corresponding to the above identification information, The above script includes the first script and the second script, How to create an invoice.

4. In paragraph 3, Further comprising a step of receiving setting information for the above output format from the user device, The above first script is for setting the output format corresponding to the above setting information. How to create an invoice.

5. In paragraph 1, Further comprising a step of receiving output status information indicating whether output of the script is successful or not from the user device after transmitting the script to the user device. How to create an invoice.

6. At least one processor; and At least one memory storing instructions that, when executed by at least one processor, cause the at least one processor to perform operations, The above actions are, The act of receiving identification information of an invoice from a user device; An operation for generating a script for outputting the invoice corresponding to the above identification information; and comprising an action of transmitting the above script to the user device; Invoice generation device.

7. In paragraph 6, The above script is written in ZPL (Zebra Programming Language). Invoice generation device.

8. In paragraph 6, The actions that generate the above script are: An action to generate a first script for setting the output format of the above invoice; and Including an action to generate a second script for outputting invoice data corresponding to the above identification information, The above script includes the first script and the second script, Invoice generation device.

9. In paragraph 8, The above actions are, Further comprising an action of receiving setting information for the above output format from the user device, The above first script is for setting the output format corresponding to the above setting information. Invoice generation device.

10. In paragraph 6, The above actions are, Further comprising an action of receiving output status information indicating whether output of the script is successful or not from the user device after transmitting the script to the user device. Invoice generation device.

Images