FIELD OF INVENTION

THIS invention relates to a system for managing an order between a client and a supplier, typically within the context of a cross-border, export-import transaction involving logistics and trade finance. BACKGROUND OF INVENTION

Online platforms to facilitate cross-border, export-import transactions are well known. However, these tend to focus on only some elements of the overall transaction. For example, Flexport provides a dashboard that includes information regarding the status of an order, active quotes, active shipments, and outstanding invoices, but does not include notifications or any information regarding required actions. Regarding shipments, Flexport includes movement details, shipment notes, a visual timeline and costs, but does not allowing searching, the placement of new orders, or information regarding placed orders or orders in transit. Flexport is relatively comprehensive in terms of quotes and billing, but has no foreign exchange (forex) tool. Similarly, other known platforms, such as FreightHub, focus on particular aspects of the transaction, but excludes others.

In addition, these platforms are all customised platforms run and managed by the related owner of the platform. This, in turn, means that a particular party to the transaction, such as a logistics service provider (LSP), is prevented from offering a full solution for the transaction to its own customers, from start to finish.

It is thus an aim of the present invention to provide a fully comprehensive platform to facilitate these types of transactions, which can be implemented as a white label product to enable a plurality of parties to implement the platform as if it were their own.

SUMMARY OF INVENTION

According to the invention there is provided a computer-implemented system for managing an order between a client of a white label operator and a supplier, once the order has been concluded between the client and the supplier, the system comprising: an order capture module comprising a processor and a memory device, the memory device including instructions which, when executed by the processor, enable the details of the order to be captured, typically using a graphical user interface (GUI), including details of the client and the supplier, the supplier’s payment terms, details of the product that is the subject of the order, logistics details regarding the movement of the product from the supplier to the client, and related logistics rates, and trade finance details in respect of the order; an order management module comprising a processor and a memory device, the memory device including instructions which, when executed by the processor, cause the processor to: collate and display a log of all actions taken by an operator in respect of the order, typically ordered by date with the latest log being displayed on top, within a window generated and displayed on the GUI; enable documents generated in respect of the order to be retrieved

(typically from a database) and displayed on the GUI; and enable comments raised by the operator in respect of the order to be retrieved and displayed on the GUI; and a white label interface, comprising a processor and a memory device, the memory device including instructions which, when executed by the processor, enable the client of the white label operator to access at least the order capture module via a white label platform associated with the white label operator.

In an embodiment, the system includes an interface, typically an application program interface, that pulls the necessary information required by the order capture module from a plurality of service providers, including a trade finance service provider, a foreign exchange service provider, a logistics service provider and an insurance service provider.

In an embodiment, the memory device of the order management module includes instructions to cause the processor to allow the operator to create and/or save new documents and comments, in respect of the order, in a database. In an embodiment, the memory device of the order management module includes instructions to select a plurality of saved orders, to enable the operator to add documents and/or comments that can be replicated across all selected orders. In an embodiment, the memory device of the order management module includes instructions to update all actions taken by an operator in respect of the order and/or to receive status updates from the operator in respect of the order.

In an embodiment, the memory device of the order management module includes instructions to determine and display upcoming deadlines or actions required in respect of the order, either based on predetermined rules or entered by the operator using the GUI.

In an embodiment, the system includes a calculator module comprising a processor and a memory device, the memory device including instructions which, when executed by the processor, cause the processor to determine an estimated landing cost (ELC) in respect of the order, typically before the order is concluded between the supplier and the client. In an embodiment, the calculator module communicates with the order capture module to enable the ELC to be determined, with the instructions causing the processor to display a breakdown of the ELC on the GUI, in total for the order and/or on a per unit basis, including supplier costs, logistic costs, customs charges, and finance costs.

In an embodiment, the order management module includes a logistics module comprising a processor and a memory device, the memory device including instructions which, when executed by the processor, cause the processor to construct and display, on the GUI, a summary of the transit of the product from the supplier to the client. This summary includes dates of all steps in the transit, including date estimates of future events, and notifications regarding past delays and/or expected future delays in the transit.

In an embodiment, once the order has been completed and the product has arrived at the client, the instructions on the memory device of the calculator module include instructions which, when executed by the processor, cause the processor to determine the actual landing cost (ALC). In an embodiment, the calculator module communicates with the order management module to enable the ALC to be determined, with the instructions causing the processor of the calculator module to display a breakdown of the ALC, in total for the order and/or on a per unit basis, including supplier costs, logistic costs, customs charges, and finance costs.

In an embodiment, the system includes a reporting module comprising a processor and a memory device, the memory device including instructions which, when executed by the processor, cause the processor to generate various reports. In one version, the reporting module is arranged to generate a cost comparison report to compare the ELC and the ALC, including supplier costs, logistic costs, customs charges, and finance costs.

In an embodiment, each white label platform includes a client GUI that has a finance module comprising a processor and a memory device, the memory device including instructions which, when executed by the processor, cause the processor to determine and display the client’s facility exposure and utilization, and forex-related details.

A computer-implemented method for managing an order between a client of a white label operator and a supplier, once the order has been concluded between the client and the supplier, the method comprising: receiving and capturing details of the order to be captured, typically using a graphical user interface (GUI), including details of the client and the supplier, the supplier’s payment terms, details of the product that is the subject of the order, logistics details regarding the movement of the product from the supplier to the client, and related logistics rates, and trade finance details in respect of the order; collating and displaying a log of all actions taken by an operator in respect of the order, typically ordered by date with the latest log being displayed on top, within a window generated and displayed on the GUI; enabling documents generated in respect of the order to be retrieved (typically from a database) and displayed on the GUI; enabling comments raised by the operator in respect of the order to be retrieved and displayed on the GUI; and providing a white label interface to enable the client of the white label operator to access at least the order capture module via a white label platform associated with the white label operator. In an embodiment, the method includes pulling the necessary information, using an application program interface, from a plurality of service providers, including a trade finance service provider, a foreign exchange service provider, a logistics service provider and an insurance service provider. In an embodiment, the method includes determining and displaying upcoming deadlines or actions required in respect of the order, either based on predetermined rules or entered by the operator using the GUI.

In an embodiment, the method comprises determining an estimated landing cost (ELC) in respect of the order, typically before the order is concluded between the supplier and the client, and once the order has been completed, determining the actual landing cost (ALC), and displaying a breakdown of the ALC, in total for the order and/or on a per unit basis, including supplier costs, logistic costs, customs charges, and finance costs.

A computer-readable medium or media having stored thereon computer-readable instructions which when executed by at least one processor performs the operations of: receiving and capturing details of an order between a client of a white label operator and a supplier, once the order has been concluded between the client and the supplier, typically using a graphical user interface (GUI), including details of the client and the supplier, the supplier’s payment terms, details of the product that is the subject of the order, logistics details regarding the movement of the product from the supplier to the client, and related logistics rates, and trade finance details in respect of the order; collating and displaying a log of all actions taken by an operator in respect of the order, typically ordered by date with the latest log being displayed on top, within a window generated and displayed on the GUI; enabling documents generated in respect of the order to be retrieved (typically from a database) and displayed on the GUI; enabling comments raised by the operator in respect of the order to be retrieved and displayed on the GUI; and providing a white label interface to enable the client of the white label operator to access at least the order capture module via a white label platform associated with the white label operator.

In an embodiment, the instructions, which when executed by the at least one processor, are further arranged to perform the operation of pulling the necessary information, using an application program interface, from a plurality of service providers, including a trade finance service provider, a foreign exchange service provider, a logistics service provider and an insurance service provider.

In an embodiment, the instructions, which when executed by the at least one processor, are further arranged to perform the operation of determining and displaying upcoming deadlines or actions required in respect of the order, either based on predetermined rules or entered by the operator using the GUI.

In an embodiment, the instructions, which when executed by the at least one processor, are further arranged to perform the operation of determining an estimated landing cost (ELC) in respect of the order, typically before the order is concluded between the supplier and the client, and once the order has been completed, determining the actual landing cost (ALC) and displaying a breakdown of the ALC, in total for the order and/or on a per unit basis, including supplier costs, logistic costs, customs charges, and finance costs.

BRIEF DESCRIPTION OF DRAWINGS

The invention will now be further described, by way of example, with reference to the accompanying diagrammatic drawings.

In the drawings:

Figure 1 shows a schematic configuration of a system for managing an order between a client of a white label operator and a supplier, in accordance with the invention; Figure 2 shows a schematic configuration of the key components or modules of an order management module used in the system shown in Figure 1 ;

Figure 3 shows a screen shot of a GUI controlled by an order capture module used in the system shown in Figure 1 ;

Figure 4 shows a screen shot of a GUI controlled by the order management module;

Figures 5 to 14 show screen shots of further features of the invention, in use;

Figure 15 shows a schematic block diagram representing a computer- implemented method for managing an order between a client of a white label operator and a supplier, once the order has been concluded between the client and the supplier; and

Figure 16 shows a diagrammatic representation of a machine in the example form of a computer system in which a set of instructions for causing the machine to perform any one or more of the methodologies discussed herein, may be executed. DETAILED DESCRIPTION OF AN EXAMPLE EMBODIMENT

The following description of the invention is provided as an enabling teaching of the invention. Those skilled in the relevant art will recognise that many changes can be made to the embodiment described, while still attaining the beneficial results of the present invention. It will also be apparent that some of the desired benefits of the present invention can be attained by selecting some of the features of the present invention without utilising other features. Accordingly, those skilled in the art will recognise that modifications and adaptations to the present invention are possible and can even be desirable in certain circumstances, and are a part of the present invention. Thus, the following description is provided as illustrative of the principles of the present invention and not a limitation thereof.

Referring first to Figure 1 , a computer-implemented system 10 is provided for managing an order between a client 12 of any one of a plurality of white label operator 14 and a supplier 16, typically once the order has been concluded between the client

12 and the supplier 16.

The system 10 comprises an order capture module 20 to enable the details of the order to be captured, typically using a graphical user interface (GUI) 30 of the type shown in Figure 3. As indicated in Figure 3, the captured details include:

- details 32 of the client 12 and details 34 of the supplier 16;

- the supplier’s payment terms 36;

- details 38 of the product/s 40 (shown in Figure 1 ) that is/are the subject of the order; - logistics details 42 regarding the movement of the product 40 from the supplier 16 to the client 12 (which is the particular GUI 30 shown in Figure 3), and related logistics rates 44; and

- trade finance details 46 in respect of the order.

Regarding the logistics details 42 in this example, as shown in GUI 30, there is a freight details 50 sub-category, including freight mode 52, the agreed Incoterm 54, the collection address 56, the port of load 58, the relevant currency 60, the delivery address 62 and the port of discharge 64. An order and shipment 70 sub-categoryis also provided, including the order date 72 and the cargo handover date 74.

Turning back to Figure 1 , the system 10 further comprises an order management module 80. As shown in Figure 2 and the GUI 82 in Figure 4, the order management module 80 comprises a log component 84 that is arranged to collate and display a log 86 of all actions taken by an operator or administrator of the system 10, in respect of the order. As shown in the GUI 82 in Figure 4, the log 86 is typically ordered by date 88 with the latest log being displayed on top, within a window generated and displayed on the GUI 82. The order management module 80 futher comprises a documents component 90 to enable all documents 92 generated in respect of the order to be retrieved typically from a database 94 (as shown in Figure 1 )) and displayed on the GUI 82. The order management module 80 further comprises a comments component 96 to enable comments 98 raised by the operator in respect of the order to be retrieved, typically from the database 94, and displayed on the GUI 82. The order management module 80 may further be arranged to allow the operator to create and/or save new documents 92 and comments 98, in respect of the order, in the database 94.

As shown in Figure 1 , to implement the invention, there is provided a processor 100 and a related memory device 102, the memory device 102 including instructions which, when executed by the processor 100, perform the functions of the order capture module 20 and the order management module 80, as described above. Other arrangements may of course be used, including a processor and a related memory device in respect of each of the modules 80, 82 described above.

The order management module 80 further comprises a selection component 104 to enable the operator to select a plurality of saved orders, to enable the operator to add documents and/or comments that can be replicated across all selected orders. The order management module 80 further comprises an updating component 106 to update all actions taken by an operator in respect of the order and/or to receive status updates from the operator in respect of the order. The order management module 80 further comprises a workflow component 108 to determine and display upcoming deadlines or actions required in respect of the order, either based on predetermined rules or entered by the operator using the GUI 82. Turning back to Figure 1 , the system 10 includes a calculator module 110 that is arranged to determine an estimated landing cost (ELC) 1 12 in respect of the order, typically before the order is concluded between the supplier and the client 12. An example of the ELC is shown in Figures 5 and 6. In an embodiment, the calculator module 1 10 communicates with the order capture module 20 to enable the ELC 112 to be determined. The calculator module 1 10 is typically arranged to display a breakdown of the ELC 1 12 on the GUI 82, in total for the order (as shown in Figure 5) and/or on a per unit basis (as shown in Figure 6).

Figure 5 for example shows the shipment details 1 14, origin details 1 16, destination details 118, and fees and interest details 120. A summary of the order is set in Figure 5, including a description 122 of the product 40 that is the subject of the order, the quantity 124, the foreign supplier unit price 126, the local unit price 128, the associated import unit costs 130, the landed Rand unit price 132 (in this case, using South Africa as the destination, having the Rand as the local currency), and the total (estimated) landed cost 134.

A more detailed breakdown is shown in Figure 6, including supplier costs 140, LSP (i.e. logistics) costs 142, customs charges 144, and finance costs 146. This information may be presented in many different ways, with Figure 7 showing one such way, in which each charge item is shown as a percentage of the total cost per charge. The order management module 80 further comprises a logistics module 148 to construct and display, on the GUI 82, a summary of the transit of the product 40 from the supplier to the client 12. This feature is related to a reporting module 150, which is arranged to generate and present various reports, as shown in Figures 8 to 13.

Figure 8, for example, shows a trade lifecycle 152, comprising a series of actions 154 and related dates 156. In this case, the actions 154 includes an advance payment 157, a balance of supplier payment 158, cargo handover 160, onboarding 162, cargo arrival 164, goods delivery 166 and payment to the relevant financial institution 168.

Figures 9 and 10 show a GUI 170 with features from the client’s 12 perspective. At a high level, the GUI 170 has the following components or features: orders 172, shipments 174, forex 176, drawdowns 178, deliveries 180 and facility exposure and utilization 182. On the left of the GU1 170, a summary of the client’s 12 financial facility 184 is shown, comprising the client’s 12 relationship manager 186 at the relevant financial institution, the outstanding amount 188 due to the foreign supplier, the forward cover booked 190, the forward cover exposure 192, the facility 194 granted to the client 12, the facility drawdown 196, the facility remaining 198 and the utilization percentage 200.

The GUI 170 in Figure 9 in particular focuses on the facility exposure and utilization 182 feature. This screen sets out the current and future facility exposure and related utilization over time. In particular, this screen shows the expected drawdowns, when repayments 202 will be required, and periods 204 when the utilization may exceed the facility limit. In particular, the next repayment (and related date) is highlighted in the bubble 206.

The GUI 170 in Figure 10 in particular focuses on the forex 176 feature. This screen sets out the relevant details 208 of the forex implications in respect of the client 12, and a related forex summary 210.

Figure 1 1 , for example, shows a shipment summary 212, including the port of load 214 (and related date), departure details 216, the current location of the vessel 218, the port of discharge 220 and the expected delivery date 222. Any significant delays 224 are highlighted and explained; in this case, there was a 3 hour delay due to bad weather. This summary 212 thus includes dates of all steps in the transit, including date estimates of future events, and notifications regarding past delays and/or expected future delays in the transit. This summary 212 also includes details of the order.

Figure 12, for example, shows a summary 226 of all vessels that will be arriving within the next seven days. This will be of particular interest to the operator or administrator of the system 10, which in this case is a member of the relevant financial institution. The dashboard 228 includes information regarding all vessels, all related clients, and all related suppliers, and a high level summary of the statuses of all vessels e.g. all departed, all in transit, all arrived etc.

Figure 13, for example, shows a summary 226 of all upcoming payments within the next fourteen days. Again, this will be of particular interest to the operator or administrator of the system 10. Each payment entry 228 includes details regarding the client, the supplier, the value, and related details regarding the shipment and financial arrangement. In an embodiment, once the order has been completed and the product 40 has arrived at the client 12, the calculator module 1 10 is arranged to determine the actual landing cost (ALC) 230. In this regard, in one version, the calculator module 1 10 communicates with the order management module 80 to enable the ALC 230 to be determined. The calculator module 1 10 displays a breakdown of the ALC 230, of the type shown on the right hand side of Figure 14, in total for the order and/or on a per unit basis, including supplier costs, logistic costs, customs charges, and finance costs.

The reporting module 150 can be prompted to generate and display a cost comparison report 232, shown in Figure 14, to compare the ELC and the ALC, including supplier costs, logistic costs, customs charges, and finance costs.

The functionalities of the abovementioned modules 1 10, 148, 150 are controlled by the processor 100 and related memory device 102, the memory device 102 including instructions which, when executed by the processor 100, perform the functions of these modules. As indicated above, other arrangements may of course be used, including a processor and a related memory device in respect of each of the modules 1 10, 148 and 150 described above.

Turning back to Figure 1 , the system 10 further includes a white label interface 240, comprising a processor 242, a memory device 244 and a related database 245. The memory device 244 includes instructions which, when executed by the processor 242, enable the client 12 of the white label operators 14 to access at least the order capture module 20 via a corresponding plurality of white label platforms 246, each platform 246 typically associated with a particular white label operator 14. Typically, the white label operator 14 is a logistics service provider, but could of course be any other provider or operator.

The system 10 further includes an interface 250, typically an application program interface (API), that pulls the necessary information required by the order capture module 20 from a plurality of service providers or operators 252, including a trade finance service provider 254, a foreign exchange service provider 256, a logistics service provider 258 and an insurance service provider 260.

In one version, a supplier module 262 is provided, comprising a processor and a memory device (not shown), the memory device including instructions to enable the order capture module 20 and/or order management module 80 to pull required information and/or details regarding the supplier 16 and/or order directly from the supplier’s system, via the API 250. In an embodiment, each white label platform 246 includes a client GUI that has a finance module 264 comprising a processor and a memory device (not shown), the memory device including instructions. The instructions cause the processor to connect with the reporting module 150, to determine and display the client’s facility exposure and utilization, and forex-related details, as described above with reference to Figures 9 and 10. Figure 15 shows a schematic block diagram representing a computer-implemented method 270 for managing an order between a client 12 of a white label operator 14 and a supplier 16, once the order has been concluded between the client 12 and the supplier 16.

The method 270 comprises receiving and capturing details of the order to be captured, typically using a graphical user interface (GUI), as indicated by block 272. As described above, the details include the details of the client 12 and the supplier 16, the supplier’s payment terms, details of the product 40 that is the subject of the order, logistics details regarding the movement of the product 40 from the supplier 16 to the client 12, and related logistics rates, and trade finance details in respect of the order.

The method 270 further includes collating and displaying a log of all actions taken by an operator in respect of the order, as indicated by block 274. The log is typically ordered by date with the latest log being displayed on top, within a window generated and displayed on the GUI.

The method 270 further includes enabling documents generated in respect of the order to be retrieved (typically from a database) and displayed on the GUI, as indicated by block 276.

The method 270 further includes enabling comments raised by the operator in respect of the order to be retrieved and displayed on the GUI, as indicated by block 278. The method 270 further includes providing a white label interface to enable the client of the white label operator to access at least the order capture module via a white label platform associated with the white label operator, as indicated by block 280. Referring now to Figure 16 of the drawings which shows a diagrammatic representation of a machine in the example of a computer system 300 within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed. In other example embodiments, the machine operates as a standalone device or may be connected (e.g., networked) to other machines. In a networked example embodiment, the machine may operate in the capacity of a server or a client machine in server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine may be a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a network router, switch or ridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated for convenience, the term“machine” shall also be taken to include any collection of machines, including virtual machines, that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.

In any event, the example computer system 300 includes a processor 302 (e.g., a central processing unit (CPU), a graphics processing unit (GPU) or both), a main memory 304 and a static memory 306, which communicate with each other via a bus 308. The computer system 300 may further include a video display unit 310 (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)). The computer system 300 also includes an alphanumeric input device 312 (e.g., a keyboard), a user interface (Ul) navigation device 314 (e.g., a mouse, or touchpad), a disk drive unit 316, a signal generation device 318 (e.g., a speaker) and a network interface device 320.

The disk drive unit 316 includes a non-transitory machine-readable medium 322 storing one or more sets of instructions and data structures (e.g., software 324) embodying or utilised by any one or more of the methodologies or functions described herein. The software 324 may also reside, completely or at least partially, within the main memory 304 and/or within the processor 302 during execution thereof by the computer system 300, the main memory 304 and the processor 302 also constituting machine-readable media. The software 324 may further be transmitted or received over a network 326 via the network interface device 320 utilising any one of a number of well-known transfer protocols (e.g., HTTP).

Although the machine-readable medium 322 is shown in an example embodiment to be a single medium, the term "machine-readable medium" may refer to a single medium or multiple medium (e.g., a centralized or distributed memory store, and/or associated caches and servers) that store the one or more sets of instructions. The term "machine-readable medium" may also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the present invention, or that is capable of storing, encoding or carrying data structures utilised by or associated with such a set of instructions. The term "machine- readable medium" may accordingly be taken to include, but not be limited to, solid- state memories, optical and magnetic media, and carrier wave signals.

While the invention has been described in detail with respect to a specific embodiment and/or example thereof, it will be appreciated that those skilled in the art, upon attaining an understanding of the foregoing may readily conceive of alterations to, variations of and equivalents to these embodiments.

The present invention according provides a fully comprehensive platform to facilitate the transactions envisaged above, which can be implemented as a white label product to enable a plurality of parties to implement the platform as if it were their own.