Method and system for constructing price structures for complex products and services

• US 7,343,325 B2
• Filed: 02/15/2002
• Issued: 03/11/2008
• Est. Priority Date: 02/15/2002
• Status: Expired due to Term

• Current Assignee: Teranet Incorporated (Teranet Holdings LP)
• Original Assignee: Teranet Enterprises Ltd.
• Inventors: Shaver, Allan B., Conville, Cameron, Krasnay, John, Kostoff, Mike, Goldberg, Dov
• Primary Examiner(s): Kramer; James A.
• Assistant Examiner(s): Greimel; Jocelyn
• Application Number:
  US10/077,683
• Publication Number:
  US 20030158784A1
• Time in Patent Office: 2,216 Days
• Field of Search: 705/400, 705/31
• US Class Current: 705/14.1
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: G06Q 30/0207 Discounts or incentives, e.g. coupons or rebates
• CPC Class Codes: G06Q 30/0283 Price estimation or determination
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes

Abstract

The invention provides a system and method for constructing and maintaining a price structure for an e-commerce transaction relating to a complex product or service. A pricing tree is built of “price components” which include discrete revenues, price adjustments, taxes, and disbursements (such as royalties). Separate revenue streams, which may be allocated to different service providers, may have independent adjustment, tax, and disbursement treatments. Attributes may also be used in the calculation of separate components. Time-date adjustments and rate package adjustments are also supported. The system allows both automated calculation and accounting using the pricing tree. Transactions are supported by a modular e-commerce back-end platform.

Claims

1. A method of providing a price structure for a transaction relating to a complex product or service to be provided by multiple providers in a business relationship, within an electronic commerce back-end platform, and comprising:

providing a product administration interface for the providers to define their respective revenue streams for the product or service, and to collaboratively define business rules to determine a price structure of a tangible product provided by one or more of the multiple providers or a service rendered by one or more of the multiple providers;

providing a customer interface for performing a transaction with respect to the product or service at a transaction price;

providing within a computer memory, responsive to both the product administration interface and the customer interface, a pricing tree of price components for a unit of each transaction with respect to the product or service, the components comprising;

a first revenue stream representing funds to be distributed in whole or in part to a first provider; and

a second revenue stream representing funds to be distributed in whole or in part to a second provider; and

the revenue streams altogether making up the transaction price;

wherein the components stay discretely allocated in the pricing tree, and wherein the components of the pricing tree are stored independently from the product or service, and wherein the components are automatically accounted for within the computer memory to permit the funds to be distributed at predetermined.

2. The method of claim 1, wherein the components further comprise a first price adjustment applied to one or both of the first revenue stream and the second revenue stream.

3. The method of claim 2, wherein the first price adjustment comprises a discount.

4. The method of claim 2, wherein the first price adjustment comprises a surcharge.

5. The method of claim 2, wherein the components further comprise a second price adjustment applied to one or both of the first revenue stream and the second revenue stream in addition to the first price adjustment.

6. The method of claim 5, wherein the first price adjustment and second price adjustment are applied in a predetermined sequence.

7. The method of claim 5, wherein the first price adjustment and second price adjustment are applied in the sequence resulting in the lowest resulting price.

8. The method of claim 1, wherein the components further comprise a first tax applied to one or both of the first revenue stream and the second revenue stream.

9. The method of claim 8, wherein the components further comprise a second tax applied over the first tax.

10. The method of claim 1, wherein the components further comprise at least one disbursement, comprising a part of the first revenue stream or the second revenue stream allocable to the first provider or the second provider, the disbursement being allocated as a component without affecting the transaction price.

11. The method of claim 10, wherein the disbursement comprises a royalty.

12. The method of claim 11, wherein the royalty comprises a fixed or variable amount.

13. The method of claim 1, wherein a component comprises at least one attribute.

14. The method of claim 13, wherein the attribute is a price-affecting attribute.

15. The method of claim 13, wherein the attribute is a non-price-affecting attribute.

16. The method of claim 1, wherein the method further includes applying a time/date argument to calculate a component.

17. The method of claim 1, wherein the method further includes applying a rate package argument to calculate a component.

18. The method of claim 1, wherein the method comprises a method of constructing and maintaining a price structure for a transaction relating to an electronically-delivered government service or product.

19. The method of claim 18, wherein the first revenue stream comprises a statutory revenue stream and the second revenue stream comprises a value-added revenue stream.

47. The method of claim 1, wherein the product administration interface is constructed to permit changes to the business rules to reflect changes in the business relationship, or in the providers, without the need to reprogram the back-end platform.

20. A system for providing a price structure for a transaction relating to a complex product or service to be provided by multiple providers in a business relationship, the system operating within an electronic commerce back-end platform, and comprising:

a product administration interface capable of receiving definitions from the providers of their respective price components and accepting business rules that have been collaboratively defined by the providers for manipulating their components, wherein the business rules are used to determine a price structure of a tangible product provided by one or more of the multiple providers or a service rendered by one or more of the multiple providers;

a customer interface capable of receiving information from a customer initiating the transaction with respect to the product or service at a transaction price;

a processor, in communication with the product administration interface and the customer interface, and executing software, the software comprising;

a pricing tree builder using the business rules for building a pricing tree of components for each transaction with respect to the product or service, the pricing tree including;

a first revenue stream representing funds to be distributed to a first provider;

a second revenue stream representing funds to be distributed to a second provider; and

the revenue streams altogether making up the transaction price;

and

a computer storage in communication with the processor for storing the business rules and components and the information, the storage capable of storing the components discretely in the pricing tree, and wherein the components of the pricing tree are stored independently from the product or service, to permit the funds to be distributed at predetermined intervals to the providers and to permit periodic reporting to the providers.

21. The system of claim 20, wherein the components further comprise a first price adjustment applied to one or both of the first revenue stream and the second revenue stream.

22. The system of claim 21, wherein the first price adjustment comprises a discount.

23. The system of claim 21, wherein the first price adjustment comprises a surcharge.

24. The system of claim 21, wherein the components further comprise a second price adjustment applied to one or both of the first revenue stream and the second revenue stream in addition to the first price adjustment.

25. The system of claim 24, wherein the first price adjustment and second price adjustment are applied in a predetermined sequence.

26. The system of claim 24, wherein the first price adjustment and second price adjustment are applied in the sequence resulting in the lowest resulting price.

27. The system of claim 20, wherein the components further comprise a first tax applied to one or both of the first revenue stream and the second revenue stream.

28. The system of claim 27, wherein the components further comprise a second tax applied over the first tax.

29. The system of claim 20, wherein the components further comprise at least one disbursement, comprising a part of the first revenue stream or the second revenue stream allocable to the first provider or the second provider, the disbursement being allocated as a component without affecting the transaction price.

30. The system of claim 29, wherein the disbursement comprises a royalty.

31. The system of claim 30, wherein the royalty comprises a fixed or variable amount.

32. The system of claim 20, wherein a component comprises at least one attribute.

33. The system of claim 32, wherein the attribute is a price-affecting attribute.

34. The system of claim 32, wherein the attribute is a non-price-affecting attribute.

35. The system of claim 20, wherein the software further comprises a time/date determiner for selectively applying a time/date-based business rule.

36. The system of claim 20, wherein the software further comprises a rate package determiner for selectively applying a rate package-based business rule.

37. The system of claim 20, wherein the system comprises a system for constructing and maintaining a price structure for a transaction relating to an electronically-delivered government service or product.

38. The system of claim 37, wherein the first revenue stream comprises a statutory revenue stream and the second revenue stream comprises a value-added revenue stream.

39. The system of claim 20, wherein each business rule comprises an expression.

40. The system of claim 39, wherein the expression includes at least one operator selected from the group consisting of:

if, and, not, or, <

, >

, mm, max, +,−

, *, /, ( ).

41. The system of claim 39, wherein the software includes an expression parser for parsing a plurality of nodes within an expression.

42. The system of claim 20, wherein the electronic commerce back-end platform comprises a modular platform for supporting an electronic commerce front-end application, the platform comprising modules for pricing, billing, accounting, collection and customer care, the modules being in communication with each other within the platform.

43. The system of claim 42, wherein the modules comprise Enterprise Java Bean™

(EJB) components.

44. The system of claim 42, wherein the software is in communication with an accounting module for passing component values to accounts in the accounting module.

45. The system of claim 42, wherein the software is in communication with a collections module to pass the resulting price to the collections module for initiating a collection from a customer.

48. The system of claim 20, wherein the product administration interface is constructed to permit changes to the business rules to reflect changes in the business relationship, or in the providers without the need to reprogram the back-end platform.

46. A software program stored on a computer-readable medium, the software program comprising:

a pricing tree builder for providing a pricing tree of price components for a customer transaction with respect to a tangible product provided by one or more providers or a service rendered by one or more providers, the components being passed to the software from business rules defined collaboratively by multiple providers of a complex product or service in a business relationship with values passed to the software from a customer interface, wherein the business rules are used to determine a price structure of the tangible product or rendered service, the components representing the business relationship between the multiple providers and including;

a first revenue stream representing funds to be distributed to a first provider;

a second revenue stream representing funds to be distributed to a second provider;

the revenue streams altogether making up a transaction price payable by the customer; and

wherein the components are discretely stored during and after the transaction in the pricing tree, independently from the product or service itself, to permit the funds to be distributed at predetermined intervals to the providers and to permit periodic reporting to the providers.

49. The software program of claim 46, wherein the pricing tree builder is constructed to permit changes to the business rules to reflect changes in the business relationship, or in the providers without the need to reprogram the software program.