Deliveries

A delivery links what you sell on the gateway to what the student receives in your Cademí. It says which products the student receives, for how long, following which release schedule and with which tags. The delivery charges nothing: payment happens on the gateway.

The idea in one minute

Gateway 1

Gateway 2

Gateway 3

Delivery

Showcase A

Product C

Product A

Product B

The delivery sits halfway, between the sale and the student.

• On one side, the sale. It comes from the gateway and carries the product identifier on the gateway.
• In the middle, the delivery. It links that identifier to what the student receives and says for how long, following which release schedule and with which tags.
• On the other side, the products. They are what the student receives, one by one or as a whole showcase.

When a sale arrives, Cademí looks for the delivery with the same identifier and creates the student's enrollment in it. The enrollment is the student inside the delivery.

The most important rule: the enrollment does not keep a copy of the delivery. It looks at the delivery every time. If you change the delivery, you change the access of every student who already came in through it. That is why a new cohort of the same course calls for a new delivery, not an edit to the current one.

How a sale becomes access

Cademí does not charge anyone. Payment happens on the gateway (Hotmart, Kiwify, Eduzz, Stripe and others). The gateway notifies Cademí of each sale through the delivery's Postback URL. Cademí reads the product identifier that came with the sale, finds the delivery that holds that identifier and creates the student's enrollment.

Each delivery has these parts:

One identifier, one delivery

• A sale finds its delivery by the exact identifier, on that gateway. Uppercase and lowercase matter. Part of an identifier does not stand for the whole identifier.
• A delivery can hold several identifiers: the product, the offer, the plan. Any of them grants the same package.
• Each identifier can be in only one active delivery per gateway. For two offers to grant different things, you need two deliveries.

No delivery, no access

If a sale arrives with an identifier no delivery has, it is recorded with an error and releases nothing. After creating or fixing the delivery, reprocess the sale in Sales → Sales.

The path from a sale to an enrollment:

The enrollment points to the delivery: what the student receives is always what the delivery says now.

How Cademí finds the sale's student

Before creating the enrollment, Cademí checks whether the buyer already has a student record in your account. That way, the same person does not get two records. The access also does not go to a record the student never signs in to.

1. Email comes first. It is what the student signs in to the student area with. So the access goes to the record where they will look for it. The comparison ignores uppercase and spaces.
2. The document comes next. Cademí only searches by document when the purchase email has no record yet. This catches the common case of someone buying again with another email, or with a mistyped one. The purchase goes to the record the person already has, instead of creating a second one. Dots and dashes in the CPF do not count.
3. More than one record with the same email or document. The oldest prevails, since it holds the student's history.
4. No record found. An approved sale creates the student, with the name, email, phone and document that came from the gateway. A communication that approves nothing (a cancellation, a pending payment) creates no one. If the account reached its student limit, the sale ends up with an error.
5. The enrollment is not repeated either. The same sale, the same subscription or a delivery given to the student by hand is updated, not duplicated. A new purchase of the same offer is a new enrollment. That is how periods add up.

Cademí never merges two records that already exist. Some accounts allow several records with the same document (a setting made by Cademí support). In those accounts, the document search does not happen: a new email always creates a new student.

What the student receives: Delivered content

The Delivered content section shows your platform as a tree. The first row, Full access to all products, delivers the entire platform. Below it come the showcases (and showcase groups), each with its products.

• Turning on a product delivers only that product.
• Turning on a showcase delivers every product in it, including the ones you add to it later. The showcase's products become covered and lose their own switch.
• Turning on Full access to all products delivers everything, including the products created later.

The summary on the left says what the delivery is delivering: Delivers the entire platform., Delivering 3 products in 1 showcase, or No content selected yet.

To find an item in the tree:

• Filter showcases and products searches by name;
• Delivered only shows just what is turned on;
• Collapse showcases hides the products inside the showcases.

Heads up: this is where most mistakes happen. Coverage is live. The student's enrollment points to the delivery and does not keep a copy of the product list. Carla sells her "English Course" to the March cohort. In June, she opens a new cohort and adds a bonus course to the same delivery. Result: the March cohort also gets the bonus. Adding or removing a product in the delivery changes the access of every student who already came in through it. To avoid this, create a new delivery for the new cohort.

For how long: One-time sale or Subscription

One-time sale

• Each product turned on shows the Access Time column. It starts as lifetime access.
• Keep it or choose an amount of hours, days, weeks, months or years.
• Time counts from the start of the enrollment.
• Months and years follow the calendar: one month from January 31 ends on February 28.

Subscription

• The Access Time column does not appear.
• Access lasts while the gateway reports the subscription as paid.
• In case of cancellation or late payment, the gateway sets the end of access.
• Any duration the delivery had is ignored.

In both modes

Access is removed automatically when the gateway reports a cancellation or refund. In a cancelled subscription, the removal happens on the end date the gateway sends.

Some gateways only work with subscriptions: on those, Sales Mode is fixed at Subscription. Other gateways have no subscriptions, and the option does not appear.

When each lesson opens: Release

A product that has a release schedule shows the Release selector on its row.

• Choose there which schedule the students of this delivery follow for that product.
• Leaving it blank keeps the product's default release.
• The selector appears even when the product is covered by a showcase that is turned on.

A schedule is shared by the deliveries that use it. Editing the schedule changes the calendar of all of them.

Tags

In Tags, choose the tags the student receives when coming in through this delivery. You can create a new tag right there, from the selector. It is born selected, and the link is saved when you save the delivery.

Tags are applied at the moment of the sale. Changing the delivery's tags applies to the next sales, not to those who already bought. Unlike products, tags are not live.

To apply the current tags to those who already came in, use Add to students who already have this Delivery, when editing the delivery. The action:

• adds the missing tags to every student with active access through this delivery;
• never removes a tag;
• leaves out the students whose access is inactive (refunded, cancelled).

Heads up: applying tags to the students who already have the delivery is retroactive and in bulk. It cannot be undone all at once.

Gateway connection

The Gateway connection section holds what Cademí receives from the gateway and what the gateway receives from Cademí:

• Product ID: the identifiers the gateway assigns to each product or offer. Some gateways show their own name for this field. Paste one or several.
• Token: on some gateways, the key that validates the incoming sales. If you already registered the token in another delivery, pick it in Use an already registered token.
• Postback URL: the address you paste into the gateway, in its webhook or postback settings. It is how each sale reaches Cademí.

The Instructions button opens the gateway's step by step. Where to find the identifier and where to paste the URL on each gateway is in Payment gateways.

After the first sale, the section shows Last sale received with the date, or No sale received yet. If the last sale arrived with an error, the section says so and offers See sales with errors.

Step by step: create a delivery

1. In the dashboard, open Sales → Deliveries.
2. Click New Delivery.
3. In Select a Gateway, pick the platform you sell on. The screen groups the gateways into Recent (the ones your account already uses), Main and Others. It also has a search by name. If your gateway is not there, use Contact us.
4. In Delivery Name, enter a name that helps you recognize it later. The name of the product or offer on the gateway is usually enough.
5. In Sales Mode, choose One-time sale or Subscription, matching the product on the gateway.
6. In Tags, choose the tags the student receives. This step is optional.
7. In Gateway connection, paste the Product ID and, if there is one, the Token.
8. Copy the Postback URL and paste it into the gateway.
9. In Delivered content, turn on the products or showcases the sale releases.
10. On each product turned on, set the Access Time (one-time sale) and, if there is one, the Release.
11. Click Save now, in the footer bar.

Nothing is saved halfway. The delivery is only written when you save, with everything on the screen. If a required field is missing (name, mode, identifier or token), the screen points to the field.

The delivery does not save in two cases:

• the identifier is already in another active delivery on the same gateway. The message says an offer with that Product ID already exists;
• the identifier is a subscription identifier that was in an archived delivery. It cannot be reused.

The deliveries list

In Sales → Deliveries:

• the search takes a name, a gateway or a product ID;
• the Gateway and Type filters narrow the list;
• each row shows the gateway, the name, the identifier, the Access column and the type (One-time sale or Subscription);
• Access says how many accesses the delivery has granted, with the share that is active.

A delivery with no product turned on shows the No access configured warning. Its sales are processed, but the student receives no product.

How do Deliveries work? reopens the diagram that explains the delivery as the distribution point of your content.

Duplicate, archive and restore

Duplicate

• Duplicate creates a copy with the same content, the same access times, the same schedules and the same tags. The name gets "(Copy)".
• The copy is born without the Product ID and without the Token. That way, it finds no sale before you fill it in.
• The schedules are the same as the original's. A new cohort with its own calendar needs a new schedule in the copy.

Archive

Archive takes the delivery out of use:

• it stops processing new sales;
• it can no longer be granted to a student by hand;
• access already delivered does not change;
• refunds and cancellations that arrive later still find the enrollment.

The delivery goes to Archived, in the corner of the list.

Restore

Restore, inside Archived, brings the delivery back. It resumes processing the sales received. Restoring fails if another active delivery on the same gateway started using the same Product ID.

To stop selling an offer

To stop selling an offer and keep the students who already have access, archive the delivery. Do not revoke the accesses. Do not reuse a subscription identifier in a new delivery.

Good to know

Frequently asked questions