USPatentGranted
B1

Methods and apparatus for optimizing markdown pricing

Granted 12 Jul 2011 · 4 office actions

Application
11/158,264
filed 21 Jun 2005
Publication
Not published
not published
Patent· this page
US 7,979,299
granted 12 Jul 2011

Life of the patent

11 dated events
⤢ drag to zoom20062008201020122014201620182020202220242026ProsecutionOwnershipTerm & fees
ProsecutionOwnershipTerm & feeshover for detail · click to open

Abstract

The invention provides methods and apparatus for optimizing markdown scheduling that group multiple retail sites into bins (or buckets) for purposes of scheduling markdown pricing on an item (or group of related items) sold by those sites. The groupings can be based, for example, on a metric that is a function of the current inventory of the item (or items) and its expected sales at each site. A markdown schedule is generated for the combined grouping of stores in each bucket, rather than for the individual stores that make up that bucket, thereby speeding price optimization determination. A report of those schedules can be used, for example, by pricing managers or other personnel to set prices at the sites. Alternatively, or in an addition, the schedules can be used in conjunction with an inventory control system to set prices for the items and/or on RFID or other electronic shelf displays.

Description

6 parts
›BACKGROUND OF THE INVENTION

The invention pertains to digital data processing and, more particularly, to methods and apparatus for optimizing determination of markdown schedules for goods sold by multiple retail sites. The invention has application, by way of non-limiting example, in facilitating pricing decisions by retailing chains and other enterprises.

Markdown pricing is the retailers' remedy for stagnant inventory. It can help move aged inventory off the shelf at the end of the selling season and/or make room for better selling items in the middle of the season. The difficulty retailers face is knowing when and how much to bring prices down. Markdowns that are too early or too severe will result in loss of profit, just as will those that are too late or too cautious.

Woo, “Markdown Management” (U.S. Patent Publication 20030229502A1, Dec. 11, 2003), assigned to the assignee hereof, suggests a markdown methodology that calls for estimating the price elasticity of sales of an item and, based on that, determining the maximum gross margin that can be attained for the item. That figure is then used in connection with setting or evaluating markdown scenarios for the item.

Grant, “Price Decision Support” (U.S. Patent Publication US20030028437A1, Feb. 6, 2003), also assigned to the assignee hereof, suggests employing a user interface to display markdown price recommendations that will achieve optimal gross margins. The user inputs proposed modifications to the recommendations and, thereby, investigates their impact, e.g., on gross margin.

While the above and other markdown technologies of the assignee have achieved widespread praise and acceptance in the industry, there remains room for improvement. Such is the case, by way of example, in determining markdown pricing for regional and national retailing chains, which may have tens or hundreds of stores, each selling hundreds or thousands of items. Prior art methodologies for determining markdown schedules for that many items across that many stores can require significant processing power and/or time.

An object of this invention, then, is to provide improved methods and apparatus for digital data processing. A more particular object is to provide such methods and apparatus for markdown scheduling.

A related object of the invention is to provide such method and apparatus as speed markdown pricing for regional, national and international retailing chains, among others, with a multitude of retail sites and/or selling a multitude of items.

Still another object is to provide such methods and apparatus as can be readily implemented in existing and future business process systems, automated or otherwise.

›SUMMARY OF THE INVENTION

The foregoing are among the objects attained by the invention which provides, in one aspect, methods for optimizing markdown scheduling of an item (or group of related items) sold by multiple retail sites—that is, stores and/or departments in a store, chain or other retail enterprise. The sites are combined into common groups (or bins or buckets) based, for example, on a metric that is a function of current inventory of the item (or items) and its expected sales at each site.

Markdown schedules are generated for the combined grouping of stores in each bucket, rather than for individual stores that make them up, thereby speeding markdown determination and reducing computational resource requirements. A report is generated showing these markdown schedules, for use, for example, by pricing managers or other personnel. Alternatively, or in an addition, those schedules can be used in conjunction with an inventory control system to set prices for the items at the retail sites, e.g., via point of sale (POS) terminals and/or RFID or other electronic shelf displays.

Further aspects of the invention provide methods as described above in which the markdown schedules are generated based on a multiplicative demand model.

Related aspects of the invention provide methods as described above in which the groupings are based on, by way of further example, a ratio of current inventory of the item(s) at each retail site to expected sales at that site.

Other aspects of the invention provide methods as described above in which the plural retail sites in each bucket are re-grouped in accord with pricing rules utilized by the respective sites. Those rules may include markdown calendars, promotion types, promotion dates, schedules of accepted markdowns, and/or pricing ladders, among others. Related aspects of the invention provide such methods in which plural retail sites in each bucket are further grouped in accord with seasonality and/or demand parameters of a demand model applicable to the respective sites.

Still further aspects of the invention provide apparatus and systems operating in accord with the methods above.

These and other aspects of the invention are evident in the drawings and in the discussion that follows.

›BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the invention may be attained by reference to the drawings, in which:

FIG. 1 depicts a retailing environment 10 in which the invention may be practiced;

FIG. 2 depicts a data flow for optimizing markdown scheduling according to one practice of the invention; and

FIG. 3 is a flow chart indicating process flow for optimizing markdown scheduling according to one practice of the invention.

›DETAILED DESCRIPTION OF THE ILLUSTRATED EMBODIMENT · 1 of 3

FIG. 1 depicts a retailing environment 10 in which the invention can be practiced. In the illustrated embodiment, that environment is a retailing enterprise of international, national, local (or other) scope comprising retail sites 12 - 18 . The enterprise can be a chain of commonly named and owned stores, though, it may be a looser (or tighter) collection of stores that are presumably (though not necessarily) under common control or management. Moreover, although the retail sites depicted and discussed here are stores, they may also be departments or other retail outlets (physical, virtual, online, or otherwise).

In the drawing, each site 12 - 18 is represented by one or more interconnected point of sale (POS) terminals 12 a - 18 c . These provide for inventory pricing, as well as for collection of money from customers at the time of sale. Though POS terminals are used for these purposes in the illustrated embodiment, it will be appreciated that in other embodiments these functions may be exercised by other means known in the art. The POS terminals are coupled to network 24 , which supports communications to an enterprise headquarters (not shown) and/or among the retail sites 12 - 18 . The network 24 may be a WAN, Internet and/or other communications medium or collection thereof (wired, wireless, land-based, satellite-based or otherwise).

Back office data store 20 represents a repository of pricing, inventory and sales information from retail sites 12 - 18 , as well as information regarding their pricing policies. This may be part of a general back office management function, e.g., that additionally includes overall corporate financial tracking and management, or otherwise.

Illustrated data store 20 comprises storage devices 20 a - 20 d which are coupled to network 24 via server and/or database management system 20 e . The data store and accompanying hardware/software platforms may be located at a single site, e.g., enterprise headquarters, or they may be distributed among multiple locations (including, the retail sites themselves).

In the illustrated embodiment, pricing, inventory and sales information, e.g., for item(s) for which markdown pricing is being optimized, is communicated from the POS terminals at each of the sites 12 - 18 to the data store 20 via router/modems 12 d , 14 d , 16 d , 18 d and network 24 . In other embodiments that information may be communicated by other means.

Pricing information communicated by the retail sites 12 - 18 to the data store 20 may include, for each item for which markdown pricing is being optimized, item identification, price history (e.g., initial, past and current), historical sales data (e.g., from past selling seasons and/or previously in the current selling season), inventory history (e.g., initial, past and current), on-shelf quantities, item type (e.g., as indicated by UPC code, or otherwise), daily sales and returns, and so forth. More generally, the communicated pricing information represents that necessary for use in determining the binning metrics described below (or other such metrics used in practice of the invention), as well as that necessary for generating markdown schedules as described below.

Pricing policy information maintained in the data store 20 reflect when and by how much the retail sites discount the various items they sell. These policies may vary from site to site, e.g., depending on geographic location, customer demographics, store type and theme, and so forth. Though other embodiments may use different and/or additional policies, those used in the illustrated embodiment include pricing ladders, markdown calendars, promotion types and dates, and acceptable markdowns. A brief explanation of these follows:

A pricing ladder is a schedule of prices used by a retail site for all or selected items (e.g., $1.95, $3.65, $7.65, $9.95, $11.95, $13.65, $17.65, $19.95, etc.). This may be based on conventional or proprietary notions of pricing psychology, applicable taxes, or other factors known in the art. A markdown calendar is a schedule of dates on which a retail site marksdown item prices. This may be absolute dates, (e.g., third Friday of every month, first day of holiday weekends, etc.), relative dates (e.g., twelve days after product introduction, thirty-five days after introduction, etc.), a combination of absolute and relative dates, or otherwise. Promotion types and dates refers to when and how a retail site will promote items storewide and/or among classes of goods, e.g., Spring fashion clearance sale, Summer sports sale, semi-annual storewide sale, and so forth. Pricing policies concerning acceptable markdowns pertain to maximum, minimum, typical, and other factors used by a retail site to determine by how much (and when) to markdown item prices. This may reflect a rule, for example, that all fashion shoes are marked down 10% six weeks after introduction, but no more than 35% within the first three months. It may further reflect, for example, that clothing accessories (such as belts, socks, etc.) are not marked down, except, during “storewide” sales.

Optimization workstation 22 comprises a personal computer, workstation, mainframe or other digital data processing system of the type commonly available in the marketplace, as programmed in accord with the teachings hereof for optimizing markdown price scheduling for item(s) sold by retail sites 12 - 18 . The workstation 22 comprises processor section 22 a (comprising a central processing unit, dynamic storage, input/output control, and the like), a monitor, keyboard and other user input/output devices 22 b , and printers or other output devices 22 c , networked or otherwise—again, all of the type commercially available in the marketplace.

The workstation 22 can be coupled for communications with back office data store 20 , via network 24 or otherwise, to gather pricing, inventory and sales information, e.g., for item(s) for which markdown pricing is being optimized, from data store 20 , directly from sites 12 - 18 , or otherwise. Workstation 22 uses that information to optimize markdown pricing determinations among all of the sites (or a portion there) in accord with the teachings hereof.

›DETAILED DESCRIPTION OF THE ILLUSTRATED EMBODIMENT · 2 of 3

The workstation can print the resulting markdown schedules, e.g., for use, e.g., by pricing managers and/or other personnel responsible for price setting. In preferred embodiments, those pricing schedules are transmitted to inventory control systems 12 e , 14 e , 16 e , 18 e at the retail sites, e.g., for use in setting prices at the POS terminals 12 a , 12 b , 12 c , 14 a , 14 b , 14 c , 16 a , 18 a , 18 b , 18 c , on electronic shelf price displays 12 e , 14 e , 16 b , 18 e at those sites, or otherwise.

FIG. 2 depicts a data flow for optimizing markdown price scheduling according to one practice of the invention. FIG. 3 is a corresponding flow chart. In general, the processing and flow depicted in these drawings occurs within optimization workstation 22 ; though, it can be executed by other digital data processing apparatus operating in accord with the teachings hereof. Some of the processing and flow, particularly, that represented in the region of FIG. 2 above the upper dashed line, represents a flow of data to workstation 22 , while that below the lower dashed line represents post-processing of the markdown schedules generated by the workstation, e.g., by inventory control systems 12 e , 14 e , 16 e , 18 e , workstation 22 , itself, or other or otherwise.

With reference to FIG. 3 , step 100 , data is input to workstation 22 representing pricing, inventory and sales information for those items sold by the retail sites 12 - 18 , . . . , for which markdown pricing is being optimized. This can be for all or a subset of the sites comprising an enterprise or other collection. The input data is used at various steps of the illustrated methodology, as will be evident in view of the discussion below.

Although the methodologies hereof can be practiced with just a few retail sites, a multitude of sites are shown in the drawing. This is to emphasize an advantage of the invention, i.e., that it facilitates markdown pricing determinations for chains (or other collections) which may have tens or hundreds of stores, each selling hundreds or thousands of items. To repeat a point made about this earlier, determining markdown schedules for that many items across that many individual stores normally requires significant processing power and/or time. The invention optimizes markdown scheduling by grouping the sites into common groups or bins and generating schedules for the combined grouping of stores in each bin, rather than for the individual stores, thereby reducing processing overhead (and time), while still optimizing gross margin achieved through sales of those items.

Though data input in step 100 may be for a multitude of items sold by the sites 12 - 18 , . . . , illustrated workstation 22 optimizes markdown scheduling for one item (or group of related items) during each iteration of steps 102 - 110 . In this regard, an item refers to a single type of good, e.g., mens' navy-colored Levi's® 517® loose boot cut jeans. Alternatively, the workstation may optimize markdown scheduling for one set a related items—e.g., mens' Levi's® and Wrangler® jeans—during each illustrated iteration. In this regard, items are considered related if their markdown schedules would be substantially similar, if optimized separately. This is typically the case for fungible items and for items that otherwise have similar pricing characteristics and that face similar demand curves. Examples include children's breakfast cereals, mens' dress shirts, women's dress shoes, and so forth.

Thus, referring to the drawings, in step 102 , the workstation begins the markdown scheduling optimization for a single item or group of related items. For sake of brevity and without loss of generality, in the discussion that follows, the term item will be used in place of the phrase item or group of items.

In step 104 , the workstation 22 computes a metric for a first level of binning (or grouping) the retail sites 12 - 18 , . . . , with respect to the item for which markdown scheduling is being optimized in the current iteration. For sake of convenience that item is referred to as the “current item” in the discussion that follows. In the illustrated embodiment, the computed metric is a function of current inventory and its expected sales. Particularly, the workstation 22 computes for each of the retail sites a ratio I′, defined as follows:

I′=I o /F o

where,

I o is the current inventory of the current item at the retail site, and F o is expected sales of the current item at the retail site at the current price which that site is selling the item. In alternate embodiments, another price may be used, e.g., initial sales price.

This metric, I′, is particularly suited for embodiments, such as those illustrated here, where markdown scheduling is based on a multiplicative demand model; though it can be used in connection with other demand models. Moreover, it will appreciated that metrics other than I′, as computed above, can be used in the illustrated embodiment. More generally, other metrics can be used where markdown scheduling is optimized in accord with the teachings hereof, whether using a multiplicative demand model or otherwise.

In the illustrated embodiment, F o is computed in view of the demand curve (or demand function) experienced by the site for the current item. It is calculated by integrating expected sales of the item according to the demand curve between the current time, t o , and the end of the selling period, or outdate, toot, for the item:

F 0 =∫ t 0 t out S ( p cur ,t )

where, S(p cur ,t) is the demand curve as a function of the current price p cur and time.

Calculation of I′, as defined in the illustrated embodiment, for all sites 12 - 18 , . . . , can be thought of as producing a histogram-like curve of the number of sites at each value of I o +F o . Put another way, it can be thought of as the number of sites that are equally close (or far), from (a) selling out inventory, percentage-wise, and/or (b) optimal gross margin, given the current price p cur they respectively set for the current item.

›DETAILED DESCRIPTION OF THE ILLUSTRATED EMBODIMENT · 3 of 3

When that demand curve is not known, the current item's demand curve within the enterprise as a whole or within a selected sub-group of stores (e.g., those in the same geographic location, with similar customer demographics, of like store type and theme, and so forth) can be used, as can the demand curve experienced by the industry as a whole or within a selected subset.

Referring to FIG. 2 , the illustrated embodiment utilizes a function, module or other code section (or sections) 50 , programmed in accord with conventional software engineering techniques to carry out the calculations above, in order to determine I′ for each site 12 - 18 , . . . . Results of those calculations are grouped or binned in an array, table, file or other data structure or store 52 , as shown. In instances where the calculations result in a continuum of I′ values of too fine granularity, those results are quantized to fall into a desired number of slots in structure or store 52 . That number is determined empirically, depending on the degree of optimization required of the workstation 52 and its processing resources.

In step 106 , the workstation 22 regroups the sites in each of the bins of structure/store 52 . This can based on pricing rules utilized at the retail sites and, particularly, is intended to divide the sites in each bin into groups that have in common, vis-a-vis the current item, pricing ladders, markdown calendars, promotion types and dates, and acceptable markdown policies. This can also be based on seasonality and/or demand parameters that will be used to generate markdown schedules for the respective sites in step 108 , discussed below.

In the illustrated embodiment, each of these factors are weighted equally and independently for purposes of the regrouping. In other embodiments, the factors are considered in combinations and/or weighted unequally for purposes of the rebinning. As above, this is determined empirically, depending on the degree of optimization required of the workstation 52 and its processing resources.

Results of rebinning step 106 are stored in array, table, file or other data structure or store 56 , as shown. This may constitute a set of separate structures, as shown, or a single structure, as is also the case with structure/store 52 , discussed above.

Turning, again, to FIG. 3 , in step 108 , the workstation computes markdown schedules for the combined grouping of sites in each bin or slot of structure/store 56 . This is in contradistinction to the prior art which computes such schedules for individual stores. And, it is further distinct from the prior art insofar as the groupings within each slot are selected, through the binning process discussed above, so that generation of the schedule for the collective can be performed with reduced processing time, yet, with sufficient accuracy to optimize gross margins on the current item.

Markdown scheduling for the bins of store/structure 56 can be performed using markdown scheduling techniques known in the art (though, conventionally applied in the art only to individual sites, not to groupings of sites as taught here) and implemented in function, module or other code section (or sections) 58 using conventional software engineering techniques. Though other models may be used, in the illustrated embodiment, element(s) 58 model demand at the sites for the current product using a multiplicative model, e.g., one expressed as a function of the relation:

S ( p )= B ( p o )* R ( p )* . . . .

where,

S(p) is a demand function for the item(s) for which markdown pricing is being optimized, p and p 0 are price and initial prices, respectively, B(p o ) is a base demand for item(s), R(p) is a price elasticity term for that/those item(s), . . . represents other factors in the demand model, such as, seasonality, inventory-effect, and so forth.

More particularly, the demand model used by element(s) 58 of the illustrated embodiment and, indeed, the operation of those element(s) themselves, follow the teachings of Woo et al, “Inventory and Price Decision Support” (U.S. Pat. No. 6,910,017, Jun. 21, 2005), assigned to the assignee hereof and the teachings of which are incorporated herein by reference, in which demand is expressed by the relation:

S ( t )= N o *N c *t γ *[e −(t/t pk ) a +C]

where,

S(t) represents gross sales revenues of the item(s) for which markdown pricing is being optimized, t is time; N o is a curve fitting parameter; N c is a demand multiplier representing an increase in sales that occurs when price is reduced; t pk is a time of peak sales; α and γ are curve fitting constants; and C is a residual sales rate at large values of t.

In still other embodiments, the demand model used by element(s) 58 of the illustrated embodiment and, indeed, the operation of those element(s), follows the teachings of Woo, “Markdown Management,” 20030229502A1, published Dec. 11, 2003, assigned to the assignee hereof, the teachings of which are incorporated herein by reference.

Referring to FIG. 3 , in step 110 , the workstation outputs the markdown schedules generated by element(s) 58 for the sites in the bins of store/structure 56 . That output can be by way of printed or other report showing the respective schedules for use, e.g., by a pricing manager or other personnel, in setting prices at the sites and/or other in connection with other administrative or management function. Alternatively, or in an addition, those schedules can be transmitted to the inventory control systems 12 e , 14 e , 16 e , 18 e and/or the sales terminals at the sites 12 - 18 for use in automatic price setting at point-of-sale, on electronic shelf displays, or otherwise.

Described above are systems and methods meeting the objects of the invention. Those skilled in the art will appreciate that the embodiments shown and discussed here are merely examples of the invention and that other other embodiment incorporating changes therein fall within the scope of the invention. Thus, by way of non-limiting example, it will appreciated that the invention applies equally to optimizing markdown scheduling of services. In this regard, then, the term items applies to goods (as discussed above) and services alike. By way of further example, it will be appreciate that various steps shown in FIG. 3 can be switched. Thus, the order of step 100 and 102 can be switched, e.g., if data is to be collected for one item (or group of related items) at a time; and steps 104 and 106 can be switched, e.g., to effect binning by pricing policy before binning by metrics. In view of these and other caveats.

Claims

14 · 2 independent · depth 4
1234567891011121314
14 granted claims

Classifications

4 codes
IPC · International Patent Classification
Section G — Physics
  • G06Q99/00
USPC · US Patent Classification
705/7.29705/7.35705/400

Claim changes

Soon
Coming soonHow the claims changed between publication and grant

See which claims were amended, added or cancelled during examination, with every added and removed word marked.

AmendedAddedCancelledUnchanged

The published claims of this patent are not paired with the granted ones in what we hold.

File wrapper

⤢ drag to zoom200620072008200920102011USPTOApplicantNon-final rejectionResponse after non-finalNotice of allowance
USPTOApplicanthover for detail · click to open
Pendency
6.1 y
2,212 days filing → grant
Office actions
2
non-final + final
Responses
2
1 RCE
Interviews
2
examiner interview summaries
Examiner
Beth V Boswell
art unit 3623 · TC 3600
Citations: 13 back · 18 forward

See the full prosecution history — every USPTO and applicant action on this file, in order.

Log in to unlock

Chain of title

⤢ drag to zoom20062008201020122014201620182020202220242026Owner 2
Titlehover for detail · click to open

See the full assignment history — every owner this patent has passed through, with recordation dates and reel/frame numbers.

Log in to unlock

Term & fees

See the term timeline — pendency span, in-force span, the maintenance fees paid and both computed expiry dates.

Log in to unlock

Validity challenges

See the validity challenges on record — reexaminations, IPRs and PGRs, with their institution decisions and outcomes.

Log in to unlock

Citations

See every patent this one cites and every patent that cites it back — publication, assignee, and how each one was found.

Log in to unlock