How to Extend the Trial Period (Company, B2B Online Store, and Tray)

This guide explains how the trial period works in Demander for:

1. the company (Demander Web / mobile);
2. the B2B Online Store (also known as Pedido.La);
3. the integration with Tray.

It also describes what happens during automatic renewal, the limit of up to 3 manual extensions requested via support, and how to request an extension (while still applicable).

Note

The commercial policy outlines the initial free period in the Billing Policy. This article complements that view with operational behavior (statuses, dates, and extensions).

Overview

In all cases Demander combines:

• a status (In trial, In deployment, In production, No longer used, Partner trial, etc.);
• a trial expiration date;
• an internal indicator that the period has already been renewed automatically (when applicable);
• the operational limit of up to 3 manual extensions requested via support; after the third, the status transitions automatically to In production.

As long as the status is a test status and the expiration date has not passed, usage remains enabled without production license charges. After that date, access or the module may be blocked until the status changes to deployment/production or until support extends the date — provided that the third manual extension has not yet occurred (in which case entry into production is automatic).

Rule: up to 3 manual extensions → production

We accept up to 3 manual extensions of the trial period requested through support. After the third manual extension, the company or module (B2B Online Store / Tray) automatically enters production.

In practice:

1. Only manual extensions performed by support (ticket request) count toward this limit.
2. Changing status from In trial to In deployment does not count as one of these extensions.
3. System automatic renewal is also handled separately from the count of 3 manual extensions.
4. On the third manual extension, the status automatically moves to In production — it does not remain in trial indefinitely.
5. With In production status, licensing and billing take effect according to the Billing Policy, with commercial alignment when needed.

Request a manual extension only when remaining in trial still makes sense and it is not yet the third manual extension. If go-live is imminent, prioritize aligning production entry directly with the sales team.

1. Company (Demander)

Where it appears

Company registration in Demander Web: Companies.

Partners can also see the expiration date and status in the response from the Partner API.

Company statuses

Code	Status
10	In trial
20	In deployment
30	In production
40	No longer used
50	Partner trial
99	Deleted

How to reactivate a company (partner)

If the company is in No longer used, the partner user can, in the Companies screen, change the status to In deployment or In production. It does not return to In trial or Partner trial.

Deleted is excluded: partners cannot reactivate deleted companies through this selector.

Under In deployment, the trial expiration date still applies. If that date has already passed, access remains blocked until the period is extended (workflow described here). In production does not use this date; licensing and billing take effect in accordance with the Billing Policy.

Step-by-step registration: How to inactivate a company.

Automatic period

When creating a company in trial, Demander defines an initial expiration date. The standard commercial timeframe is detailed in the Billing Policy (free period, without automatic billing renewal).

Operationally, the system may automatically extend the trial timeframe once. Additional extensions go through support and count toward the limit of up to 3 manual extensions.

Important: after the third manual extension, the company automatically enters production. There is no fourth manual trial extension. Changing status from In trial to In deployment does not count toward this limit.

Manual extension (support)

If testing must continue beyond the automatic period and it is not yet the third manual extension:

1. Open a ticket with Demander support (official customer support channel).
2. Provide the company (code / trade name).
3. Explain the justification (e.g., deployment still in progress, delayed ERP integration, client pilot).
4. Provide the estimated production go-live date (date or window).
5. Indicate, if known, how many manual extensions have already taken place.
6. Support evaluates the request and, if approved, updates the trial expiration date (and status, if needed). If this is the third manual extension, the status moves to In production automatically.

Tip

The clearer the go-live estimate, the faster the review tends to be. Extensions without estimates, or nearing the third manual extension, are typically directed toward deployment/production status with the commercial team. Remember: moving from In trial to In deployment does not consume one of the 3 manual extensions.

2. B2B Online Store (Pedido.La)

Where it appears

Screen B2B Online Store Settings.

Module details: B2B Online Store Module.

Screen fields

• Enabled until: expiration date of store testing. After this date, the store only remains operational if the status is In production (or equivalent enabled state).
• Status: In trial, In deployment, In production, No longer used, Partner trial, or Deleted.
• Store blocked: when checked, the store goes offline regardless of the date.

Automatic period

The B2B Online Store has its own testing lifecycle. In many cases the initial timeframe is around 15 days from activation, aligned with the standard for e-commerce modules documented in similar integrations (e.g., Loja Integrada).

Demander can automatically renew the store trial period once (independent of the company’s automatic renewal). Additional extensions go through support and count toward the limit of up to 3 manual extensions.

The same rule applies here: after the third manual extension, the store status automatically moves to In production. Moving from In trial to In deployment does not count.

Manual extension (support)

Same workflow as the company, specifying clearly in the ticket:

• that the extension applies to the B2B Online Store;
• store URL (.pedido.la), if applicable;
• justification and estimated production go-live of the store;
• how many manual extensions have already taken place, if known.

Support updates the Enabled until date and/or store status. If this is the third manual extension, the status moves to In production automatically.

3. Tray Integration

Where it appears

Screen Tray Integration.

Setup guide: How to configure integration with Tray.

Automatic period and extension

The standard is identical to other e-commerce modules: testing timeframe with possible automatic renewal and up to 3 manual extensions via support. After the third manual extension, Tray integration status moves automatically to In production (with commercial implications). Moving from In trial to In deployment does not count toward this limit.

In the extension ticket, specify:

• company and Tray store (URL);
• justification;
• estimated go-live date of the integration;
• how many manual extensions have already taken place, if known.

How to request an extension (checklist)

Use this checklist in your support ticket:

1. What to extend: company, B2B Online Store, and/or Tray.
2. Identification: company code/name; B2B store or Tray URL, if applicable.
3. Justification: objective reason why more time is needed.
4. Estimated go-live date: specific date or timeframe.
5. Current status: In trial / In deployment.
6. How many manual extensions have already taken place, if known — remember that on the third the status moves to production automatically, and In trial → In deployment does not count.

Channels: official Demander support or the channel agreed upon with the partner/sales representative.

Relation to billing and production

• Extending the trial date does not by itself place the company or module into production — except on the third manual extension, which triggers automatic production entry.
• Changing status from In trial to In deployment does not consume one of the 3 manual extensions and does not trigger production entry by itself.
• Status In production requires licensing/billing under the Billing Policy and alignment with sales.
• Status No longer used terminates usage. For the company, the partner can return to In deployment or In production in the registration, without a new automatic trial period. For modules (B2B Online Store, Tray, Loja Integrada, etc.), reactivation is usually only to In production, and there is also no new automatic trial period.

Related articles

• Billing Policy
• Registering Company in Demander Web
• How to inactivate a company
• B2B Online Store Module
• Tray Configuration
• Partner API — get company list