Create offer

Create offer is the screen where you publish an offer to your Telegram channels: you paste a product link, the application pulls out the title, the photo and the prices, you see the message just as it will reach the channel, and you publish it or leave it in the queue.

schedule 12 minute read

toc On this page expand_more

• The screen
• Paste the link and extract the data
• The fields
• Preview
• The actions
• The multi-channel panel
• The draft
• Editing from the queue or from manual handling

The screen always works on the active channel, the one the menu selector marks: the message template, the preview and the default header and footer all come from it. If you do not have a channel yet, a notice above the form tells you how to get one; Channels explains it.

---

The screen

The first time you open Create offer, a guided tour points out its parts. You can skip it, and start it again whenever you like from the help button in the header, with Repeat the tour.

On a narrow screen, the preview peeks out from the bottom edge while you fill in the form. Its header carries a chip with what matters —how many characters are over or left— and the arrow expand_less (See the preview), which scrolls down to it; once there, the arrow expand_more (Back to the form) takes you back up.

---

Paste the link and extract the data

Paste the product link into the field and press search Extract data (on a phone you will only see the magnifying glass), or press Enter in the field. The application queries the store and fills in:

• Offer title,
• Current price and, if there is one, the list price,
• Image URL.

The Description field is never filled in by itself: it is yours.

What each lookup does to the form

• Each lookup that brings data first empties the title, the prices and the image of the previous product, so two offers never get mixed. If the lookup fails, what was there stays: check it or press Clear.
• The list price is only kept if it is higher than the current price; if the store returns one that is equal or lower, the field is left empty.
• If you paste a text with the link inside, the lookup takes the first link it finds, but the field keeps the text: leave just the link before publishing.
• If the link is a short one (amzn.to, amzn.eu or AliExpress short links), the field is replaced with the full link.
• A link without https:// in front is understood just the same.

Which stores, and what it costs

It works with any store that has a public product page, not just Amazon and AliExpress. Which lookups spend credits, how many, and which spend nothing is explained in Stores and affiliation. If you run out of them, a notice below the link says so and you can keep publishing: you type the title and the price yourself.

The affiliate link

If there is an affiliate rule for that store, or the lookup went through the Amazon or AliExpress API with your code, the affiliate link is built by itself. It is not shown on screen: the field keeps showing the product link, and the link with your code is the one that travels inside the message.

When the link is not going to carry your code, an amber notice appears below the field. You can publish anyway: the notice only tells you that this offer will not earn you a commission.

What the notice says in each case

• No rule covers that store: “This link will go out without your affiliate code: none is set up for ‘store.com’.”, with a shortcut to Set up affiliates to create the rule.
• It is an Amazon or AliExpress link typed by hand and you have that store connected: it asks you to press Extract data, which is what puts your code in.
• It is a shortened link: it also asks you to press Extract data, which opens it and puts the code in.
• If you collaborate in somebody else's organization and cannot reach Settings › Affiliates, the notice says that whoever manages the organization can add the rule.

When nothing comes back

What happened is read below the link. In red when the link has to change; in amber when you can carry on by hand, and then the cursor jumps to the title by itself so you can type the data.

Each notice and what to do

What you see	What to do
“We cannot find that product. Check that the link opens its page.”	The link is not that of a specific product, the page does not exist or the application could not get either the title or the price out of it. If the link does open the page properly, type the data yourself.
“This product is not available in Spain.”, with your organization's ship-to country	AliExpress sells that product but does not ship it to that country, and that read spends no credits. If you still want to publish the offer, type the title and the price yourself. The country is chosen in Settings › AliExpress.
“Could not open the shortened link. Paste the product's full link.”	It happens with no connection or with the shortener down. Paste the full link.
“We could not read the product page just now. Try again in a moment or fill it in by hand.”	The store did not answer in time. It is also what you see when AliExpress rejects your key: if it repeats, check its credentials.
“The store has blocked data extraction. Enter the title and the price manually.”	Some large chains reject automatic reads. Insisting does not help; let us know the link from Support, because those stores can be tuned one by one.
“We could not read the product page. Write the title and the price yourself: the affiliate link is already in place.”	You have an affiliate rule for that store and the lookup returned no data —because of the store, the credentials or because you ran out of credits—. Type the data: the link goes out with your code all the same.
“Amazon is switched off in Settings and the product could not be read from the web.”	You have switched off Amazon's API and the web lookup could not read it either. The notice links to Settings › Amazon.
“We could not read the AliExpress product page…”	Without your credentials, the page could not be read at that moment, and no credit is spent. Write the title and the price yourself, or set your credentials: the notice links to Settings › AliExpress.
A notice about the Amazon credentials or AliExpress's tracking ID	They are missing or not valid, and the notice says so in those words. Fix them in the section it links to.
“You have run out of credits for reading product pages. Enter the title and the price yourself, or see Subscription for how to get more.”	Type the title and the price yourself, or get more from See the subscription.

---

The fields

Field	Required	What it accepts
Product URL	Yes	The link to the product page. It is the field in the Paste the link block.
Offer title	Yes	Up to 255 characters. The first thing read in the channel.
Current price	Yes	Just the figure, with a comma or a period: 89,99. It has to be greater than 0.
List price	No	The price before the discount. It cannot be lower than the current price; if there is no reduction, leave it empty.
Coupon	No	One or more codes, separated by commas or spaces. Up to 100 characters.
Image URL	No	The address of the photo, starting with https://.
Header	No	Up to 50 characters. A text at the start of the message, for example a category.
Footer	No	Up to 250 characters. A text at the end, for example a signature or the channel link.
Description	No	Up to 500 characters. Extra information that goes in the body of the message.

Field formats and notices

• Prices understand both thousands formats: 1.299,99 and 1,299.99 are the same number. They accept at most two decimals. On a phone they open the numeric keypad.
• A list price equal to the price is accepted, but the field warns in amber that the message may go out with a 0 % discount: if there is no discount, leave it empty.
• A repeated coupon is not accepted: “You entered ‘CODE’ twice.”.
• Pressing Enter in any other one-line field does not publish anything.
• If an extracted value is longer than the field allows, it is cut to the limit.

Preset header and footer

Next to Header and Footer there is a bookmark Presets button that opens your organization's preset texts; they are set up in Settings › Message. If there are none, the menu says “No preset texts”.

When you open the screen, the two fields come filled in with the active channel's default texts. As soon as you type in them or choose another preset text, that text becomes yours and is the one that gets sent; what happens to them in a send to several channels is explained in The multi-channel panel.

When a field is flagged

A field with an error is flagged in red, with a sentence saying how to fix it, when you have typed in it and leave it, or when you press a send button.

When you press a send button every one that fails is flagged and the screen takes you to the first. Filling a field with Extract data or recovering a draft does not flag it.

---

Preview

Any change to the form updates the preview half a second later. It shows:

• The image, above the text, if the image URL is valid. If the photo cannot be opened, a notice says so below its field.
• The text of the message, formatted with the channel's template. Links open in another tab.
• The state of the message, below: how much of Telegram's limit it takes, which is 1,024 characters with an image and 4,096 without. It says “Up to date” while it fits; from 90% of the limit it turns amber and counts how many are left; above the limit it turns red, says how many are over and what to shorten. At the end of the line goes the count “used / limit”.

When the preview does not update

If a field is wrong, the preview does not disappear: it keeps showing the last good version, dimmed, with “Not updated” and how many fields are left to fix. If there was none yet, below the drawing it asks you to correct what is flagged. With no connection it says “Not updated: we could not connect.”.

---

The actions

The buttons are in the page header and can be reached without scrolling the form.

	Action	What it does
delete_sweep	Clear	Empties all the fields at once, without asking, and deletes the draft. To start another offer without reloading.
share	Share	Opens the system share menu with the message ready. It only appears where the browser has it, which is phones and some desktop browsers.
schedule_send	Queue	Saves the message in the active channel's queue, to go out later.
send	Publish	Sends it right now to the active channel.
checklist	Send to several channels	Only if you have more than one channel. Opens a panel to tick the destinations.

After a successful send, the screen reloads empty —with the channel's default texts back in place— and a brief notice confirms it: “Published in ‘Channel’.” or “In the ‘Channel’ queue.”. Each channel the message reaches counts as one publication of the month. To see the message in Telegram, there is the link in Published posts, on Home.

Queue

Queue leaves the message saved in the active channel's queue, and from the Solo plan the queue sends it by itself, at its pace and in its schedule: Publication queue explains it. On the free plan the button saves the message all the same, but you publish it from the queue.

Sharing on any platform

Codingram publishes directly to Telegram; for everything else there is Share. It hands the message and, if the template generates it, the image to the system share menu, and from there you choose the app and the destination: WhatsApp, X, Facebook or any other app you have installed.

How what you share arrives

The message is shared without styles —no bold, italics or strikethrough— so it arrives fine on any platform, and with the links in full.

If the offer's image comes from the store instead of being generated by the template, only the text is shared, with the link inside. What you share is not recorded in the queue or in Published posts. If there is no preview yet because a required field is missing, Share flags them just as Publish does; if there already was one, it shares the last good version, so check that it is up to date.

When it cannot be published

Publish is disabled in two cases, and a notice above the form explains it:

• The organization's owner has not confirmed their email, and without that nothing is published. If it is you, the notice carries Resend the confirmation email (or Add an email, if you have none); if not, it says that its owner has to confirm it. Access and account explains it.
• The month's publications have run out. The notice says from which day they start again and which plan would give more. Queue still works: from the Solo plan, what you prepare goes out by itself when the month begins; on the free plan, you publish it from the queue from that day on.

When a fifth or less of the month's publications is left, a blue notice announces it: “You have 12 publications left this month. They start again on June 1.”.

Other notices that can appear above the form

Above the form also come, when they apply, the notice about the setup left unfinished and, if Telegram rejects the bot's token, a red one that takes you to Settings › Telegram to change it, or tells you that whoever administers the organization fixes it if you cannot open that section. If in your plan the queue sends by itself, whatever you send to it meanwhile goes out once it is fixed.

What it tells you when you send

What happens when you publish or send to the queue is read in a notice above the form, with a button to carry on when there is one:

• The Telegram bot is missing: Connect the bot.
• You have no channel: Go to channels. The channel lacks its ID: Complete channel.
• You have ticked more channels than your plan allows per send: See plans.
• Telegram did not accept the message in any channel: “Not published”, with the reason and Try again.
• It went out in some channels and not in others: “Published to 2 of 3 channels.”, the list of those that failed with their reason, and Try again only on those.
• A failure on our side or no connection: “What you wrote is still here” and Try again. Nothing is lost.

A problem with a field never goes in that notice: it is flagged below the field.

---

The multi-channel panel

checklist Send to several channels, to the right of the page header actions, opens a panel with one checkbox per channel. Inside, Queue and Publish appear again: those act on the ticked channels and say so with a count —“Queue (2)”, “Publish to 2”—; the ones in the page header act on the active channel, just one. With no checkbox ticked, the panel asks “Tick at least one channel.”.

How many channels one send can reach is decided by the plan: one on the free plan and on Solo, three on Creador and twelve on Agencia, and on Creador and Agencia also the additional channels you buy. With more ticked, the send is rejected and the notice says which plan raises the limit.

• Each channel receives the message with its own template, so the same product can go out in a different format in each.
• If you do not touch the header and the footer, each channel uses its default texts; if you type in them, that text is sent as it is to all of them.
• Queue with several channels puts a copy of the message in each one's queue, with its template and its affiliate link; a channel's own code is explained in Stores and affiliation.
• The preview is measured channel by channel, because each one has its own template: below it tells you in which ones it would not fit (“In ‘Channel’ it is 40 characters too long.”).

Fine print: sending to several channels

• Channels with no ID from Telegram appear disabled and marked: they cannot be a destination until you fill in the field.
• The panel remembers the channels you ticked the last time you sent to two or more, on another device too.
• History belongs to each channel: a product having already been published in one channel does not stop you from publishing it in another.

---

The draft

What you type is saved by itself in the browser. If you reload the page, change channel or come back later in the same tab, the form appears just as you left it and a notice says so: “We have brought back what you were writing”.

Fine print: when the draft is lost and what it does not keep

• The draft belongs to that tab: another tab starts empty, and closing the tab forgets it. It expires after seven days.
• It is deleted when you press Clear and when you successfully publish, queue or save. After a failed send it is kept.
• When you arrive from the phone's Share menu it is not recovered: the screen opens with the shared link.
• Editing a queued message has its own draft, separate from the new offer's.
• The checkboxes in the multi-channel panel are not part of the draft.

---

Editing from the queue or from manual handling

When you come in from the Edit button in the queue, the screen switches to edit mode:

• The fields are filled in with the saved message and the preview loads by itself.
• The title becomes Edit offer.
• The page header keeps Clear and save Save, which updates the message and returns you to the queue with the notice “Message updated”. There is no Queue, Publish, Share or multi-channel send.

If the message is gone or no longer valid

• If the message is no longer in the queue —it went out at its time or somebody deleted it—, the notice says so. If it happens before you open it, pressing Edit takes you back to the queue; if it happens while you are editing, saving offers Create a new offer, which opens Create offer empty: what you had changed does not carry over, so copy it first.
• A message that no longer meets the rules of an offer —price at 0, list price lower than the price— opens with the failing field flagged in red and, in the preview, “Fix what is marked to see the message.”, so you can correct it and save.

From the manual handling of a search profile you arrive in the same way: the offer comes filled in, the page header adds Cancel to go back, and when you publish or queue it the product is marked as handled in that channel.