A Price List is where wxrks stores the rates used to calculate what a project costs — the currency, a rate per language pair, any minimum fee, and extra cost factors like rush fees or discounts. Once a Price List is linked to an Organization and an Organizational Unit, wxrks uses it automatically to price every project created there.
​

💡 Who is this for? This guide is for the Account Admin who needs to understand how a Price List's settings affect project cost calculation and how it connects to Organizations and Organizational Units within the wxrks platform.

A Price List brings together everything wxrks needs to price a project on its own, with no manual math required: a currency, whether it charges by word or by hour, a default rate, any number of per-language-pair rates, a minimum fee, and optional Price Coefficients for extra charges like rush fees or discounts. This article covers what each of those settings means and how they interact — for the field-by-field steps to actually build one, see How to create a Price List.
​

A Price List sets what you charge a client. It's a separate concept from an Organizational Unit's Net Rate settings, which set what you pay a vendor for the same work — see All about Organizational Units for Net Rate.

Every Price List is set up in one currency, and every rate and fee on it is expressed in that currency. The Charge By toggle (Word or Hour) controls the unit those rates are measured in — a new Price List starts out priced per word; switching it to Hour is done from the Price List's own page after it's created, not at creation time.
​

The Default price per word (or per hour) is the fallback rate wxrks uses only when the Price List has no per-language-pair rates defined at all. As soon as even one language pair has its own rate, the default stops applying — see below for what happens to a pair that isn't explicitly listed once that's the case.

Once a Price List has at least one language pair priced, wxrks uses this order to price any task:
​

In practice this means a Price List with even one language pair configured no longer relies on the default rate for anything; every other pair either matches by language family or falls back to the most expensive listed pair.

The screenshot above shows a real Price List's Information tab: its Currency, its Minimum fee by mode, and the Language pair section with one configured rate. See How to create a Price List for the steps to add a pair yourself, including the price simulation panel shown next to the table.

The Minimum fee by toggle decides how a Price List's minimum fee is scoped, and it changes which field next to it applies:
​

See How to create a Price List for worked numeric examples of both modes, and Project Costs for how a minimum fee shows up once it's actually applied on a project's Costs tab.

Beyond per-language-pair rates, a Price List can define Price Coefficients — extra cost factors such as a rush fee, a client discount, or a weighting applied by Translation Memory match tier. Each coefficient has its own fee type, unit (per word or per hour, for example), and value, plus a live simulation showing exactly how it changes the price per word before you save it.
​

Once configured, a Price Coefficient becomes available as a Price List Item when adding a cost to a project — see Project Costs for how that works from the project side. For the full field-by-field walkthrough of building coefficients, see How to create a Price List.

A Price List has to be linked to an Organization before it can be linked to any of that Organization's Organizational Units — it isn't usable on a project until both links exist. This linking can be set at the moment the Price List is created, or managed afterward from any of three places:
​

A Price List can also be marked Account Default for [currency] — flagging it as the default Price List wxrks reaches for whenever a project needs a Price List in that currency and none is set more specifically at the Organization or Organizational Unit level. An Organizational Unit's own Prices tab has a separate Default toggle per linked Price List, which takes priority over the account-wide currency default for projects created under that Unit specifically.

A project's Price List is chosen in Step 2 of project creation. If the project's Organizational Unit has a Default Price List configured, this field is pre-filled automatically; otherwise it's left blank and can be set by hand.
​

A project without a Price List still gets a cost estimate — wxrks falls back to a simple baseline rate rather than leaving the cost blank — but for accurate, client-specific billing you'll want a real Price List selected. To change which Price List a project uses after it's already been created, the project first needs to be back in Draft status; see Project Costs for exactly how costs are calculated from a Price List and the logfile, and why cost controls lock once a project leaves Draft.

A Price List's own page has three tabs: Information (the settings covered above), Associations (its Organization/Organizational Unit links), and Notes — a free-text memo field for keeping SOW or agreement details next to the Price List itself.
​

Its Actions menu also offers Create a copy, which duplicates the Price List as a starting point for a similar one, and Delete Price List Permanently, which walks through an impact review and requires typing the Price List's exact name to confirm before anything is removed — unlike an Organization or Organizational Unit, a Price List can be deleted from the interface.