Skip down to the research record

GitLab order processing dates: 4 published rules

Quota Forecast Editorial Team · Published · 13 min read

Four published rules in GitLab's order-processing handbook decide when a GitLab order is processed and which close date it carries. The stage must be set before submission. The quote start date should fall inside a 30-calendar-day window, and a start date beyond that window is still approved under a separate rule. A start date more than 30 days in the future moves the close date. The distributor's purchase order must match the quote within $1.00. The rules belong to GitLab, not to any other firm, but the questions behind them transfer.

Key takeaways

  • Set the stage to 6 - Awaiting Signatures before you click Submit for Approval.
  • Keep the quote start date within 30 calendar days of the submission date.
  • Expect the close date to move when a start date is more than 30 days in the future.
  • Match the distributor PO to the quote within $1.00 (USD).

Many sales ops owners learn these rules late. A deal is marked closed-won, the close date goes into the forecast, and then the order sits for a week because a field was blank or a stage was skipped. The date you typed and the date an order is processed can be different days, and the gap is often set by rules nobody on the sales floor reads.

This post walks through those four rules, taken from GitLab's published order-processing handbook. You may never sell to GitLab, and your order desk may run its own checks. Still, the rules are a useful model. They show the questions a careful order desk asks before it accepts an order, and when it may change a close date on your behalf. If you own sales operations at a small B2B firm, you can hold your own process against the same questions.

We will follow one deal through the whole post.

The example deal we will follow

An account executive at a small firm that resells software to businesses owns an opportunity for Bluefin Logistics, a customer that wants a subscription. The customer buys through a distributor, so two documents have to agree: the quote the account executive built in the CRM, and the purchase order the distributor sends for the customer.

The customer signs the quote, and the account executive is ready to mark the opportunity as won. The quote start date falls inside the 30-day window discussed in the second rule. The sales ops owner wants the close date in the forecast to match the day the order is actually processed, not the day the customer first said yes.

That gap is the reason for this post, and for a small firm it matters more than it might for a larger one. A few large deals often carry a big share of the month, so a close date that moves by weeks can change what a revenue leader reports upward. The quote looks clean on paper. Whether the order moves on time depends on four things: the stage when the opportunity is submitted, the quote start date, the close date that comes back, and the distributor's PO. The stage, window, and PO rules decide whether an order is processed.

The example is fictional. The customer, the rep, and the firm are made up for illustration. The rules and figures come from GitLab's handbook. Check the page yourself before relying on any figure here. Handbooks change, and the version you read today may not match the version an order desk applies later.

Rule 1: Change the stage before you submit

GitLab's handbook gives a fixed order of steps for getting an opportunity approved. The stage must change to 6 - Awaiting Signatures first, and only then should Submit for Approval be clicked. The Sales Order Processing page states the sequence in substance.

For the example deal, the opportunity moves to stage 6 before anyone presses Submit for Approval. The rep does not click while the opportunity still shows an earlier stage, even if the customer's signature has just arrived by email. Sales ops should treat the stage change as part of the submission itself, not as tidying to do afterward. For the field checks before a stage change, see required-field rules before stage change.

The stage matters beyond the order desk, too. HubSpot's forecast guide notes, "You can also set up forecast categories for each of your sales pipelines or use deal stages." (HubSpot forecast setup guide) If your forecast is built on deal stages, a stage that lags behind the signature makes the forecast lag with it. The stage is a forecasting input as well as an order step.

Rule 2: Keep the quote start date inside 30 calendar days

The handbook says that orders "will be processed as long as the Quote Start Date is within 30 calendar days from date of submission." That sentence sits on the same Sales Order Processing page. Two details matter. The window is counted from the date of submission, not from the date the quote was drafted. And it is counted in calendar days, not business days.

The example quote's start date sits inside that window on the day the rep submits, so the order moves forward. The check is easy to do and easy to forget. A quote drafted some time ago can drift outside the window by the time it reaches the submit step, especially when the signature takes longer than the deal team expected.

For sales ops, the practical step is to build the window check into the submission routine. Compare the quote start date with the day the submission will actually happen. If a rep is submitting near the edge, the rep should check with the order desk before clicking rather than assume the order will be accepted. Asking is cheap. Finding out after the fact is slower and harder to fix. For a related check, see quote expiry checks.

Rule 3: A start date more than 30 days out moves the close date

The handbook pairs the window with a companion rule. It states that if the Quote Start Date is more than 30 days in the future, Order Management will approve the order and move the close date to the earliest date the opportunity can be booked. The same handbook page sets out this wording for that case.

Suppose the customer asks to start later, beyond the 30-day window. The rep updates the quote start date to match what the customer wants. The order does not stop there. Order Management approves it and sets the close date itself. The rep did not type that date, and it may not be the date the rep or the revenue leader had in mind.

This change affects a forecast more than any other rule here. The number a revenue leader sees can shift because a start date moved, even though no one in sales touched the close date. Sales ops owners should watch for that movement. When a close date changes after submission, ask two questions: did the start date move, and did Order Management make the change under this rule? If both answers are yes, the change came from the order process, so it does not by itself show that the deal slipped. For why a date moved, see close date change log.

The earliest bookable date is a date the order process can accept, not a date the customer has agreed to pay on. Treat it as the order desk's date. If the rep believes the customer will sign earlier, record that belief in the deal notes rather than overwriting the date the order process set.

Setting expectations early helps. If a customer asks for a later start, the rep can explain that the order desk will approve the order and set the close date to the earliest date the opportunity can be booked. A customer who hears it before submission is less likely to be confused when the forecast moves.

Rule 4: The distributor PO must match the quote within $1.00

The customer buys through a distributor, so its purchase order reaches GitLab through the distributor. The handbook sets a tight tolerance for that document: "The Distributor PO to GitLab must be within $1.00 (USD) of the Quote object in order to be accepted." The same handbook page carries the line.

For the rep, that means comparing the PO to the quote before submission, not after the distributor's paperwork lands in the inbox. If the quote and the PO differ by more than $1.00, the handbook's own wording says the PO is not accepted. A gap that looks trivial on screen can still matter when it sits outside the limit.

Make the check a field-level comparison. Read the total on the quote and the total on the PO, then confirm the difference is inside the tolerance. Do not rely on a summary in an email to confirm the figure, because a summary can hide the number that counts.

If the PO comes back outside the tolerance, the fix belongs with the distributor's paperwork and the quote, not with the forecast. Ask the distributor to correct the PO before anyone submits the opportunity again. Changing the close date to fit a PO that does not match will not get the order accepted, because the test is the match, not the date.

The handbook states the tolerance in US dollars. If your deals are in another currency, or your firm sells direct and never receives a distributor PO, do not borrow this figure. Ask your order desk which tolerance it applies, and write the answer into your process.

Illustrative example: a start date 40 days out

Suppose a quote's start date is 40 days after submission. That is outside the 30-day window, so the order desk approves it under the later-start rule and sets the close date to the earliest bookable date.

After submission: check the status and confirm the license

Approval is not the end of the opportunity owner's work. The handbook sets a follow-up step: confirm the customer receives the license within two days of the opportunity closing as won. The Sales Order Processing page assigns this step to the opportunity owner.

In the example, the rep is the opportunity owner, so the rep owns that confirmation. The clock runs from the moment the opportunity closes as won, so the rep should not wait for a periodic review to learn whether the license arrived. This two-day window is GitLab's rule for GitLab's teams. Your firm may set a different window, and it should set one, with a named owner, even if the number differs.

To see where an order stands after submission, the handbook points to a dashboard: "To view the status of an opportunity after it has been submitted for approval, review the 7-Closing Stage Dashboard." The same page names it. Sales ops should bookmark that view and check it on a regular cadence, not only when a revenue leader asks.

Stage position also shapes what leaders see. Pipedrive's forecast view ranks deals by pipeline position. Its guide puts it this way: "Deals that are furthest along the pipeline are prioritized at the top of your forecast view, which allows you to see the deals that are closest to being marked as WON." (Pipedrive forecast view guide) A deal left at an early stage after submission sinks in that view and can look further from closing than it really is. That is one more reason to fix the stage at the moment of submission.

In the example, the rep checks the deal on the 7-Closing Stage Dashboard after submitting, and notes the stage it shows. If the close date has moved under the third rule above, the rep checks the close date on the opportunity record before the forecast is updated.

A useful habit is to keep two dates on the deal: the date the rep expects, and the date the order process has set. The first is a forecast. The second is the one the order follows. When they differ, the notes should say why, so the revenue leader does not have to guess.

Who owns which date

Each date in this post has an owner, and some owners repeat. It helps to write them down.

Date or stepOwnerWhat must be trueSource
Stage at submissionSales ops (team's own assignment)Stage reads 6 - Awaiting Signatures before Submit for Approval is clickedSales Order Processing page
Quote start dateSales ops (team's own assignment)Falls within 30 calendar days of the date of submissionSales Order Processing page
Close date after a later startOrder ManagementMoves when the start date is more than 30 days in the futureSales Order Processing page
Distributor POSales ops (team's own assignment)Matches the quote within $1.00 (USD)Sales Order Processing page
License confirmationOpportunity ownerConfirmed within two days of closing as wonSales Order Processing page

In the example, the rep builds the quote, and the rep owns the license confirmation. The close date that Order Management can change under the third rule belongs to the order process, even though it lands in the forecast. Sales ops owns the reporting that ties these together.

Writing the owner next to each date is a small step, and it removes guesswork. When a date moves, nobody has to ask who moved it. A short owner list kept with the forecast sheet is easier to use than a long policy page few people read.

Setting close dates your order desk can work with

Before a rep marks a deal closed-won, the sales ops owner can run through five questions. None of them needs a new tool. Each one comes straight from the rules above.

  1. Is the opportunity at stage 6 - Awaiting Signatures, and was Submit for Approval clicked after the stage changed?
  2. Is the quote start date within 30 calendar days of the day of submission?
  3. If the start date moved later, has the close date changed, and does the forecast show the new date?
  4. If a distributor is involved, does the PO match the quote within $1.00?
  5. Who confirms the license with the customer, and when will that owner do it, given the two-day window GitLab sets?

Two warnings go with the list. First, a date that looks correct in the CRM is not proof that the order desk agrees with it. Second, a checklist works only if the people who own each date use it. Put it where the rep sees it at the moment of closing, not in a folder nobody opens.

Once a month, or whenever the team reviews the forecast, pull the deals whose close dates changed after submission. Look for patterns. Are start dates drifting outside the window, or are POs failing the tolerance? A short list of those patterns shows the team where its process needs attention, and gives the revenue leader a clear answer when a forecast number moves.

GitLab's rules are specific to GitLab, and your firm's rules will differ in the details. The shape of the work is the same, though. A close date is set by a sequence of checks, and some of those checks belong to people outside sales. The best sales ops owners learn those checks, write them down, and keep the forecast honest about the dates the order process has actually set.

Your next step

Before your next submission, check that the stage reads 6 - Awaiting Signatures and that the quote start date falls within 30 calendar days of the submission date. Write both checks in the deal notes.

Related guides: Compare close dates: 3 rules for date and time fields · 4 Stripe renewal date rules to check before quarter close.

Frequently asked questions

Does the stage have to change first?

Yes. The handbook says the stage must change to 6 - Awaiting Signatures before the Submit for Approval button is clicked.

Does a start date more than 30 days out stop the order?

No. Order Management approves it and moves the close date to the earliest date the opportunity can be booked.

Sources