---
layout: default_v3
language: default
permalink: 
i18n_link: 9735
updated: 2026-01-02
#--- article key-values ---#
collection: default_articles
category: restaurant-management
tags: Par levels, Set par, Set par levels
type: article
page_id: 9735
hreflang_id: 9735
date_published: 2025-12-31
date_modified: 2026-01-02
#--- javascript schema ---#
javascript_schema:
 - script: jquery_3_2_0_min
 - script: bootstrap_min
 - script: article_infinite_scroll
 - script: article_mix_infinitescroll
 - script: article_mix
 - script: article_mix_faq
 - script: article_mix_toc
#--- section schema ---#
section_schema:
 - section: nav-main_menu
 - section: nav_submenu_iconview_v2
 - section: article_body_v2
 - section: footer
 - section: footer-sticky_cta_bar
 - section: schedule_demo_cta
#--- page key-values ---#
meta_tags:
  t_meta_title: How to Set Up Par Levels in a Restaurant
  t_meta_description: Learn how to set up par levels step-by-step to prevent stockouts, reduce waste, simplify ordering, and keep inventory consistent week to week.
  t_meta_abstract: Learn how to set up par levels step-by-step to prevent stockouts, reduce waste, simplify ordering, and keep inventory consistent week to week.
  i_meta_image: og_how-to-set-up-par-levels-in-a-restaurant.png
article_body:
  json-ld_article:
    v_date_published: 2025-12-31
    v_date_modified: 2026-01-02
  author:
    p_author_id: 254
    t_author: Derrick McMahon
    p_author_url: derrick-mcmahon.html
    i_author: 254.jpg
    t_author_description: Derrick McMahon is a writer and restaurant technology enthusiast. He holds a Bachelor&amp;amp;amp;#039;s degree in Hospitality Management from UNLV, where he developed a passion for the food service industry.
    p_author_facebook: //www.facebook.com/altametrics/
    p_author_twitter: https://twitter.com/https://twitter.com/altametrics?lang=en
    p_author_linkedin: 
    p_author_instagram: 
  podcast_section:
    v_links: 
    podcast_links: 
      - t_title: Iheart Radio
        v_url: 
        i_icon: iheart_radio_icon.png
      - t_title: Amazon Music
        v_url: 
        i_icon: amazon_music_icon.png
      - t_title: Youtube Music
        v_url: 
        i_icon: youtube_music_icon.png
      - t_title: Spotify
        v_url: 
        i_icon: spotify_icon.png
  feature_snippet:
    p_type: text
    t_title: What is a par level in a restaurant?
    t_description: A par level is the target amount of an item you want to keep on hand to get through normal business until your next delivery (plus a small buffer).
  content:
    heading:
      t_title: How to Set Up Par Levels in a Restaurant
      t_description: Learn how to set up par levels step-by-step to prevent stockouts, reduce waste, simplify ordering, and keep inventory consistent week to week.
      image:
        i_image: set-up-par-levels-1767201427-4603.png
        t_image_description: 
        v_image_attribution: 
        v_image_license: 
      v_video:
    paragraphs:
      - t_headline: Understanding Par Levels
        t_text: A <strong>par level</strong> is your restaurant's "comfort zone" for inventory. It's the target amount you want on hand so you can run service smoothly until your next order arrives. Think of it like setting the right fuel level for your business - too low and you stall - too high and you waste money and space.<br><br>Here's the simplest way to understand it - <strong>par is not the amount you order - it's the amount you want to end up with.</strong> Ordering is just the action you take to get back to par after you count what you already have.<br> Par levels matter because most inventory problems fall into one of two buckets -<br><br><strong>1. Stockouts (running out) -</strong> This is when you 86 menu items, scramble with substitutions, send staff to a store, or disappoint guests. Stockouts also create hidden costs - extra labor, rushed prep, lower ticket averages, and more mistakes under pressure.<br><br><strong>2. Overstocks (ordering too much) - </strong>This ties up cash in product sitting on shelves. It crowds your storage areas, makes counts harder, increases the chance of spoilage, and can lead to "use it before it goes bad" decisions that hurt food quality and consistency.<br><br>Par levels help you avoid both because they create a repeatable routine -<strong> (1)</strong><strong>count (2) compare to par (2) order what you need</strong>. Once that routine is in place, ordering becomes less emotional and more consistent.<br><br>Par levels apply to more than just food. You should set pars for -<br><br><strong>- Core ingredients</strong> (proteins, produce, dairy, dry goods)<br><strong>- Prep items</strong> (sauces, portioned sides, dough, batters)<br><strong>- Beverages</strong> (soda syrup, coffee, bar inventory)<br><strong>- Disposables</strong> (to-go boxes, cups, lids, bags, gloves)<br><strong>- Cleaning and chemicals</strong> (sanitizer, detergent, paper towels)<br><br>When you set pars across these areas, you don't just "manage inventory." You protect your sales, your team's workflow, and your guest experience - every single shift.<br><br>
        p_headline_type: h2
        image:
          i_image: 
          t_description: 
          v_attribution: 
          v_license: 
        callout_text:
      - t_headline: What You Need Before You Set Pars
        t_text: Before you start calculating par levels, you need a clean foundation. If you skip this part, your pars will look "right" on paper but won't work in real life - because the item list is messy, units don't match, or deliveries don't follow a predictable rhythm. <br><br>Here's what to get in place first -<br><br><strong>1) A clean item list (only what you actually order)</strong><br>Start with every product you buy regularly - ingredients, beverages, disposables, and cleaning supplies. Remove duplicates (example, Tomatoes - Roma vs. Roma Tomatoes), and make sure each item has one clear name. If the same item comes from two vendors, still keep it clean - either list them separately by vendor or standardize to one primary vendor.<br><br><strong>2) Consistent units of measure</strong><br>This is where many restaurants get stuck. You can't set a par if you count in "each" but order in "cases," or you count in "pounds" but the invoice is in bags. Choose a standard unit for each item and stick to it -<br><br>- Chicken. Case<br>- Ground beef. Case or pounds (but be consistent)<br>- Lettuce. Case<br>- Flour. Bag<br>- Gloves. Box<br>- To-go containers. Case<br><br>Also record <strong>pack size</strong> (example. "1 case = 6 -10 cans" or "1 case = 4 x 1-gallon jugs"). This makes ordering math simple and prevents under-ordering.<br><br><strong>3) Your delivery rhythm and vendor rules</strong><br>Write down -<br><br>- Delivery days (Mon/Thu, etc.)<br>- Order cutoff times<br>- Typical lead time (same day? 2 days? 5 days?)<br>- Minimum order requirements<br>- Common substitutions and out-of-stocks<br><br>Par levels depend heavily on <strong>how many days you need to cover between deliveries</strong>. A restaurant with daily delivery will have very different pars than one that gets a truck twice a week.<br><br><strong>4) A storage map (where items live)</strong><br>Par levels work best when your storage is organized. Assign each item a home location- walk-in, freezer, dry storage, bar, paper goods shelf, chemical cage. If items constantly move around, counts become inaccurate and pars stop being reliable.<br><br><strong>5) One person responsible for the system</strong><br>Par levels fail when "everyone kind of owns it." Assign ownership by area (kitchen manager, bar lead, GM, etc.). That doesn't mean one person does every count - it means one person is accountable for keeping pars updated and followed.<br><br>Once these pieces are in place, the actual par setup becomes simple and repeatable.<br><br>
        p_headline_type: h2
        image:
          i_image: what-you-need-before-you-set-pars-1767204628-9400.png
          t_description: restaurant inventory
          v_attribution: restaurant inventory
          v_license: wERWR234
        callout_text:
        call_to_action:
          p_type: purchase
          t_title: Elevate Your Restaurant's Operations
          t_text: Swift Inventory Solutions with Altametrics!
          t_button_text: Book a Demo
          p_button_url: https://altametrics.com/schedule-demo.html
          p_button_color: ff0000
          v_form_id: 
          v_product: altametrics
          background:
            type: image
            i_image: https://wp.altametrics.com/assets/images/cta/264-Image_Gradiant.png
            p_video: 
            p_color: FFA500
      - t_headline: Step 1. Group Items the Right Way
        t_text: If you build par levels as one giant list, you'll hate using it - and your team will avoid it. The easiest way to make pars workable is to <strong>group items the same way you store them and the same way you count them</strong>. That way, par checks feel quick and natural instead of overwhelming.<br><br>Here's a simple, restaurant-friendly way to group inventory - <br><br><strong>1) Group by storage area first</strong><br>Start with the physical flow of your restaurant. Most places have - <br><br><strong>- Walk-in cooler</strong><br><strong>- Freezer</strong><br><strong>- Dry storage</strong><br><strong>- Bar / beverage</strong><br><strong>- Paper goods / disposables</strong><br><strong>- Chemicals / cleaning</strong><br><br>This is the fastest way to count because you can walk the space in order and avoid jumping between areas.<br><br><strong>2) Then group by category within each area</strong><br>Inside each storage area, break items into categories that match how you think and prep -<br><br>- Proteins (chicken, beef, seafood)<br>- Produce<br>- Dairy<br>- Dry goods (rice, flour, spices)<br>- Sauces/condiments<br>- Frozen items<br>- Bakery/bread<br><br>This helps you spot problems faster. For example, if produce is constantly under par but proteins are always over, you'll see that pattern quickly.<br><br><strong>3) Separate "menu-critical" items from "flex" items</strong><br>Not every item carries the same risk. Flag your <strong>menu-critical items - </strong>the products that directly cause an 86 if you run out. Examples -<br><br>- Your main protein (chicken, beef patties)<br>- Signature sauce<br>- Buns/tortillas<br>- Fries or rice (depending on concept)<br><br>Then identify <strong>flex items - </strong>things you can substitute without breaking the menu (within reason). This doesn't mean you ignore them; it just means your buffer and review attention should be higher on menu-critical items.<br><br><strong>4) Flag high-risk items</strong><br>High-risk items deserve extra structure because mistakes cost more. Mark items that are -<br><br><strong>- High cost</strong> (steaks, seafood, specialty spirits)<br><strong>- High waste</strong> (berries, fresh herbs, dairy-heavy items)<br><strong>- Long lead time</strong> (specialty products, vendor-brought items)<br><strong>- High volume</strong> (fries, chicken, to-go containers)<br><br>For these items, your par should usually include a more intentional buffer and more frequent checks.<br><br><strong>5) Assign "par ownership"</strong><br>A par system works when someone feels responsible for keeping it accurate. Assign an owner by group -<br><br>Kitchen manager. walk-in + freezer<br>Lead cook. prep items + sauces<br>Bar lead. liquor + wine + beer<br>Shift lead. paper goods/disposables<br>Maintenance/manager. chemicals/cleaning<br><br>When you group items this way, your par sheet becomes a tool your team can actually use - fast counts, fewer misses, and clear accountability. Now you're ready to set starting pars without guesswork.<br><br>
        p_headline_type: h2
        image:
          i_image: 
          t_description: 
          v_attribution: 
          v_license: 
        callout_text:
      - t_headline: Step 2. Calculate a Starting Par Level
        t_text: This is the part most owners overcomplicate. You don't need perfect forecasting - you just need a reasonable starting point based on what you actually use. Your first par level is a <strong>baseline</strong>, and you'll adjust it as you learn.<br><br><strong>Start with a simple timeframe<br></strong>Use a recent window that reflects normal business -<br><br><strong>- Last 2-4 weeks</strong> is a solid starting point<br>- Avoid weird weeks (major holidays, a one-time catering event, shutdowns) unless that's your typical reality<br><br>If you don't have clean inventory usage data, you can still estimate using purchase history, prep sheets, or POS mix (you'll refine later).<br><br><strong>Step A. Find your average daily usage</strong><br>Pick an item (example- chicken thighs, burger buns, fries). Estimate how much you go through per day.<br><strong>Basic method -</strong><br><br>- Total used over the period / number of days = <strong>Average Daily Usage</strong><br><br>Example -<br>- You used 12 cases of burger buns in 14 days<br>- Average daily usage = 12 / 14 = <strong>0.86 cases/day</strong><br><br>If cases feel too clunky, convert to a unit that's easier -<br>- 1 case = 120 buns<br>- 0.86 cases/day = 103 buns/day (roughly)<br><br>The goal isn't perfection - it's "close enough to stop guessing."<br><br><strong>Step B. Determine your coverage window</strong><br>Your par needs to cover the time between deliveries <strong>plus a buffer</strong>.<br>Coverage window =<br><br><strong>- Days between deliveries</strong> (including weekends if vendors don't deliver)<br><strong>- Safety buffer</strong> (usually 10-25% or 1 extra day for critical items)<br><br>Example -<br>- You get deliveries twice per week (every 3-4 days)<br>- Your practical coverage window might be <strong>4 days + 1 buffer day = 5 days</strong><br><br><strong>Step C- Use the starting par formula</strong><br><br><strong>Starting Par = Average Daily Usage x (Days of Coverage + Safety Buffer)</strong><br>Example -<br><br>- Average daily usage. 0.86 cases/day<br>- Coverage + buffer. 5 days<br>- Starting par. 0.86 x 5 = <strong>4.3 cases</strong><br><br>Round to something usable- <strong>4 or 5 cases</strong>, depending on pack sizes and risk.<br><br><strong>What if you don't have history?</strong><br>If you're new, launching a menu item, or switching vendors, estimate pars using - <br><br>- Similar item usage (swap "new sauce" with old sauce demand)<br>- Recipe usage + projected sales<br>- Conservative starting pars + more frequent checks the first 2 weeks<br><br>Once you do 2-3 order cycles, you'll have real patterns - and that's when pars get powerful.<br><br>
        p_headline_type: h2
        image:
          i_image: 
          t_description: 
          v_attribution: 
          v_license: 
        callout_text:
      - t_headline: Step 3. Set Reorder Points and Order-To Targets
        t_text: Once you have a starting par, the next step is making it usable during ordering. That's where <strong>reorder points</strong> and <strong>order-to targets</strong> come in. These two numbers keep you from waiting too long to order (stockouts) or ordering too early (overstock).<br><br><strong>Par (Order-To) vs. Reorder Point - the simple difference</strong><br><br><strong>Par / Order-To Level -</strong> The amount you want to have after your order arrives and gets put away. This is your target "full tank."<br><strong>Reorder Point (ROP) -</strong> The amount where it's time to place an order so you don't run out before the next delivery hits.<br><br>In many restaurants, owners set a par and stop there - but without a reorder point, you end up ordering inconsistently based on how busy you "feel."<br><br><strong>How to set a reorder point</strong><br> A reorder point should cover your expected usage during the vendor's lead time (plus a small buffer).<br> <strong>Reorder Point = Average Daily Usage x Lead Time Days (+ buffer for critical items)</strong><br> Example -<br><br>- You use 10 gallons of fryer oil per week = 1.4 gallons/day<br>- Lead time is 2 days<br>- ROP = 1.4 x 2 = 2.8 gallons<br>- Round up. <strong>3 gallons</strong><br>- Meaning. if you're at 3 gallons on hand, it's time to reorder.<br><br>For menu-critical items, add a little extra (or use one extra day). For items you can substitute (like some dry spices), you can keep the buffer smaller.<br><br><strong>Ordering math that actually works</strong><br> When it's time to order, use a simple "order-to" approach -<br><br><strong>Order Quantity = Par (Order-To) On-Hand On-Order</strong><br><strong>On-Hand.</strong> what you count right now<br><strong>On-Order.</strong> what you already placed but haven't received yet (very important to avoid double-ordering)<br><br>Example -<br>Par level for chicken. 10 cases<br>On hand. 6 cases<br>On order. 2 cases<br>Order quantity = 10 - 6 - 2 = <strong>2 cases</strong><br><br>This is the core of a par-based ordering system. It removes guessing.<br><br><strong>Handling pack sizes and rounding rules</strong><br>Vendors sell in cases, bags, boxes, and jugs - not in "2.3." Your par system needs a consistent rounding rule -- If it's a <strong>high-risk stockout item</strong>, round up (better to have a little extra than 86)- If it's a <strong>high-waste item</strong>, round down and count more often <br><br>When you set reorder points and order-to targets correctly, you're not just "doing inventory." You're building a repeatable ordering process that protects sales and cash flow.<br><br>
        p_headline_type: h2
        image:
          i_image: step-3-set-reorder-points-and-order-to-targets-1767204629-1475.png
          t_description: restaurant inventory
          v_attribution: restaurant inventory
          v_license: weRWER23423
        callout_text:
        call_to_action:
          p_type: purchase
          t_title: Transform Your Restaurant Operations Now!
          t_text: Effortless Inventory Tracking with Altametrics!
          t_button_text: Request a Demo
          p_button_url: https://altametrics.com/schedule-demo.html
          p_button_color: FF0000
          v_form_id: 
          v_product: altametrics
          background:
            type: color
            i_image: 
            p_video: 
            p_color: 008000
      - t_headline: Step 4. Build Your Par Sheet
        t_text: A par system only works if your team can use it quickly during real shifts. That's why the best par sheet is not fancy - it's <strong>clear, organized, and consistent</strong>. Whether you build it in Excel, Google Sheets, or inside your inventory tool, the goal is the same - make counting and ordering simple.<br><br><strong>Start by building the sheet around how you count</strong><br> Don't build one massive list that mixes walk-in items with paper goods and bar inventory. Instead, set it up in sections that match your storage areas -<br><br>- Walk-in cooler<br>- Freezer<br>- Dry storage<br>- Bar / beverage<br>- Disposables<br>- Chemicals / cleaning<br><br>Most restaurants find it easiest to create <strong>one tab per storage area</strong>, or at least one section per area. That way, a manager can walk the space top-to-bottom and fill it out fast.<br><br><strong>Use a "minimum required" set of columns</strong><br> These columns cover 95% of what you need without clutter -<br><br><strong>1. Item name</strong><br><strong>2. Storage location</strong> (walk-in, freezer, dry, etc.)<br><strong>3. Unit</strong> (case, bag, lb, each, box)<br><strong>4. Pack size</strong> (ex. 6 x 10 cans, 4 x 1-gal)<br><strong>5. Vendor</strong> (optional but helpful)<br><strong>6. Par / Order-To level</strong><br><strong>7. Reorder point</strong> (optional but recommended)<br><strong>8. On-hand</strong> (counted quantity)<br><strong>9. On-order</strong> (already ordered, not received)<br><strong>10 Order quantity</strong> (calculated)<br><strong>11. Notes</strong> (yield, substitutions, "count partial cases as decimals," etc.)<br><br><strong>Make the math automatic (if you're using a spreadsheet)</strong><br> If you're in Excel/Sheets, you can calculate order quantity automatically -<br><br><strong>Order Qty = Par - On-Hand - On-Order</strong><br><br>Then add a simple rule -<br><br>- If the result is negative, order 0<br>- If the item must be full-case, round up to the next whole case<br><br>Even basic automation makes your ordering more consistent and reduces mistakes.<br><br><strong>Add small details that prevent big errors</strong><br> A few simple touches keep par sheets from falling apart -<br><br><strong>- Standard counting rules</strong> (ex. "open case = 0.5 case" or "count by pounds")<br><strong>- Item naming standards</strong> (avoid duplicates that confuse ordering)<br><strong>- Pack-size reminders</strong> (so someone doesn't order "10" thinking it's each when it's cases)<br><strong>- Ownership labels</strong> by section (who counts it, who approves it)<br><br><strong>Keep it short and focused</strong><br>A par sheet is not an inventory encyclopedia. If an item is rarely used or only ordered once a month, consider keeping it on a separate "low-frequency" list. Your main par sheet should focus on items that impact weekly ordering and daily service.<br><br>Once your par sheet is built and matches how you store/count, the system becomes easy to follow - counting gets faster, ordering gets cleaner, and pars become something your team actually trusts.<br><br>
        p_headline_type: h2
        image:
          i_image: 
          t_description: 
          v_attribution: 
          v_license: 
        callout_text:
      - t_headline: Step 5. Count, Order, and Receive Using the Same System
        t_text: This is where par levels either become a real operating system - or they turn into a spreadsheet nobody trusts. The key is consistency - <strong>counting, ordering, and receiving must follow the same rules every time.</strong> If you count one way, order another way, and receive with zero checks, your on-hand numbers will drift and your pars will stop working.<br><br><strong>1) Set a counting routine that matches your operation</strong><br> You don't need to do full inventory every day. Most restaurants do best with a two-layer approach -<br><br><strong>Daily quick counts (5-10 minutes). </strong>Focus on your most critical items - primary proteins, fries/rice, buns/tortillas, signature sauces, and key disposables. This prevents mid-week stockouts and emergency orders.<br><strong>Weekly full counts (30-90 minutes). </strong>Count everything on your par sheet by storage area. Do it on the same day/time each week so the data is comparable.<br><br>If your deliveries come twice per week, you may also do a count right before ordering each time.<br><br><strong>2) Standardize how you count (so everyone counts the same way)</strong><br> Create simple "count rules" and train to them - How to count partial cases (0.25, 0.5, 0.75)<br>- Whether you count in cases, pounds, or each<br>- What to do with items pulled for catering, staff meals, or manager comps<br>- How to count items stored in multiple locations (ex. cheese in prep line + walk-in)<br><br>This prevents the common problem where two managers count the same shelf and get completely different numbers.<br><br><strong>3) Order using the par math - no gut feeling</strong><br>Once counts are done, ordering should be mechanical -<br><br>- Confirm on-hand<br>- Confirm what's already on-order (to avoid double-buying)<br>- Use <strong>Order Quantity = Par - On-Hand - On-Order</strong><br>- Round to pack sizes and vendor rules<br><br>If someone overrides the math, they should write a quick note ("big weekend event," "vendor out last week," "promo starting Friday"). That keeps adjustments intentional instead of random.<br><br><strong>4) Receive like it matters (because it does)</strong><br> Receiving is where inventory accuracy is won or lost. Use a quick receiving checklist -<br><br>- Verify quantity matches the invoice (and your order)<br>- Check quality and temps (especially proteins and dairy)<br>- Note substitutions and shorted items<br>- Confirm credits are documented if something is missing or damaged<br><br><strong>5) Put-away discipline keeps pars accurate</strong><br> Finally, items must go to their assigned locations. If product gets scattered, your next count will be wrong, and your par system will "feel broken" even though the math is fine.<br><br>When counting, ordering, receiving, and put-away are aligned, par levels become reliable - and your team stops fighting the system.<br><br>
        p_headline_type: h2
        image:
          i_image: 
          t_description: 
          v_attribution: 
          v_license: 
        callout_text:
      - t_headline: Step 6. Review and Adjust Pars Every Week
        t_text: Par levels aren't "set it and forget it." Your restaurant changes constantly - sales patterns shift, vendors run short, menu items rotate, prices jump, and seasons impact demand. If you don't review pars regularly, they drift. Then you're back to emergency orders, extra waste, and inconsistent counts.<br><br>The good news - you don't need a huge process. A simple weekly review keeps pars accurate and protects your cash.<br><br><strong>1) Pick a consistent weekly review time</strong><br> Most restaurants do best with a quick review right after -<br><br>- A weekly full count, or<br>- A major order cycle (especially if you order 2x/week)<br><br>Block <strong>15-30 minutes</strong> on the same day each week. Consistency is more important than a perfect process.<br><br><strong>2) Know what should trigger a par change</strong><br> Adjust pars when you see any of these -<br><br><strong>- Frequent stockouts</strong> (same items running out before delivery)<br><strong>- Too much backstock</strong> (walk-in packed, product expiring, shelves overflowing)<br><strong>- Waste spikes</strong> (spoilage, expired product, trim waste, over-prep)<br><strong>- Menu changes</strong> (new items, removed items, recipe changes, portion changes)<br><strong>- Promotions and catering</strong> (temporary demand increase)<br><strong>- Seasonality</strong> (weather, school schedule, holidays, local events)<br><strong>- Vendor changes</strong> (different pack size, longer lead times, less reliable fill rates)<br><br><strong>3) Use simple "red flag" questions</strong><br> You can diagnose most par problems quickly -<br><br>- Did we 86 anything this week? Why?<br>- Did we throw away anything because it expired or went bad?<br>- Did we do any emergency runs or last-minute add-ons?<br>- Are we consistently ordering the same items early (before the normal order day)?<br>-Are there items we're counting but never using?<br><br>If the answer is "yes" repeatedly for the same item, the par needs adjustment.<br><br><strong>4) Adjust in small steps, not big swings</strong><br>Avoid doubling pars based on one crazy weekend. Instead -<br><br>- Increase or decrease par by <strong>10-20%</strong> at a time, or<br>- Add/remove<strong> one day of coverage</strong> for items that swing a lot<br><br>Then re-check after the next order cycle. Small, controlled changes keep the system stable.<br><br><strong>5) Tie pars to a few operational signals</strong><br> You don't need complex KPIs, but it helps to watch <strong>- </strong><br><br><strong>- Waste levels</strong> (are you over-par on perishables?)<br><strong>- Stockout frequency</strong> (are critical items under-par?)<br><strong>- Storage capacity</strong> (is par realistic for your space?)<br><strong>- Cash flow </strong>(are you tying up money in slow movers?)<br><br>When you review and adjust pars weekly, your ordering becomes predictable, your inventory stays cleaner, and your team spends less time putting out fires - and more time running service smoothly.<br><br>
        p_headline_type: h2
        image:
          i_image: 
          t_description: 
          v_attribution: 
          v_license: 
        callout_text:
        call_to_action:
          p_type: purchase
          t_title: Get Accurate Inventory Valuations
          t_text: Manage Your Workforce with Altametrics
          t_button_text: Schedule a Demo
          p_button_url: https://altametrics.com/schedule-demo.html
          p_button_color: 0000FF
          v_form_id: 
          v_product: altametrics
          background:
            type: color
            i_image: 
            p_video: 
            p_color: FF0000
event_body:
  json-ld_event:
    t_name: Employee Scheduling for Restaurant Managers
    t_description: Attendees will learn how create excellent schedules. The class teaches managers how to estimate the number of employees they need to staff their locations; how to accurately forecast their customer demand; how to quickly and accuaratly write and communicate schedules to employees; and how to evaluate the accuracy and optimization of their schedules to make adjustments.
    v_start_date: 2022-08-08
    i_image: 
    p_location_name: Altametrics Online Webinar Course
    p_address: webinar.altametrics.com?site=altametrics
    v_price: 10.00
    t_offer_description: Priority Registration
    v_registration_url: webinar.altametrics.com?site=altametrics
faq:
  t_faq_title: Frequently Asked Questions
  faq_ask: 
    - t_question: What's the difference between par level and reorder point?
      t_answer: Par (order-to level) is where you want inventory to land after receiving an order. A reorder point is the on-hand level that tells you it's time to place an order so you don't run out before delivery.<br>
    - t_question: How do I calculate a starting par level?
      t_answer: A simple method is, Average Daily Usage x (Days Between Deliveries + Safety Buffer). Start with the last 2-4 weeks of normal sales/usage.<br>
    - t_question: Should I set pars for prep items like sauces and portioned sides?
      t_answer: Yes. Prep items cause major issues when they run out mid-shift. Set pars for high-usage prep (sauces, dressings, portioned sides) and count them on a daily or shift-based routine.<br><br>
    - t_question: How do I avoid over-ordering with par levels?
      t_answer: Make sure you always subtract on-order quantities, round appropriately, and review items that consistently expire or sit untouched. Over-ordering usually comes from bad units, bad counts, or not tracking on-order items.<br>
---
