CODFamilia
Features How it works Pricing Blog FAQ Academy Sign up Sign in

Connecting a YouCan store to your order management

How to link a YouCan store to a COD platform: authorisation, orders arriving in real time, the role of the SKU, and what to check on the very first order.

The essentials

What is it?
It is a formal link between a YouCan store and the seller's workspace. The seller authorises read access to their orders, and from then on every order placed in the store arrives by itself in the CODFamilia confirmation queue, with the customer, the city and the items.
Who is it for?
Moroccan sellers who already run a YouCan store and handle their orders cash on delivery. It is the shortest route in for them: no code, no spreadsheet, no copy-paste.
How does it work?
The seller opens the applications page, starts the connection, accepts the permissions YouCan asks for, and comes back to the platform. The platform then subscribes by itself to the store's "new order" event; each notification received is checked, converted and recorded as a lead.
What is it for?
Because the store is already where the customer types their own name, phone number and address. Re-entering that by hand adds nothing and introduces errors; letting it travel untouched protects the delivery rate.
How do you use it?
Only one thing needs preparing beforehand: product references. The SKU of every item sold in the store has to be the SKU of the matching CODFamilia catalogue product, otherwise the order arrives without knowing which product it refers to.

Connecting a YouCan store means authorising the platform once to read the store's orders, so that every new order becomes a lead with no retyping at all.

What actually crosses over, and what does not

The connection reads orders. That is all, and it is deliberate: the permissions requested from YouCan are read permissions, plus the single right to subscribe to order notifications. Nothing is written back into your store.

Information Crosses over? Note
Customer name Yes Taken from the customer, otherwise from the shipping address
Phone number Yes Checked: an invalid number holds the lead back
City and address Yes The city is matched against the delivery city list, or settled on the call
Items and quantities Yes Through the SKU of the ordered variant
Total paid by the customer Yes This is the amount the courier will collect
Customer note Yes Passed through as written, for the confirmation agent
Store catalogue No Products are not copied across: only the SKU links the two
Order status No Confirmed, shipped, delivered: nothing is written back into YouCan

The SKU, the hinge of the whole link

A YouCan order does not say "the customer wants this catalogue product". It says "the customer wants this variant of this product page in my store". The only thing both worlds share is the reference: the SKU. If it matches, the order becomes a correctly priced lead. If it does not, the order still arrives — but as a damaged lead, with the reason "unknown reference".

Two mistakes recur. The first is a variant left with an empty SKU: the platform can then only identify the product by its name, and that name matches no catalogue entry. The second is a SKU copied with an invisible difference — a trailing space, an underscore instead of a hyphen, a different case on part of the reference.

The right habit is to fix the SKU in the store, never in the lead. Fixing the lead settles one order; fixing the store settles every order after it.

Real time and the safety net

Two mechanisms run in parallel, and it is worth knowing why. The first is the notification: as soon as an order is created, YouCan calls an address specific to your connection, and the lead exists within the second. Every call is signed, and a call whose signature does not match is refused — knowing the address is not enough to make us believe in an order.

The second is a periodic re-read of the store's recent orders. It exists because a notification can be lost: a server restarting, a network cut, a transient error. YouCan only retries a small number of times; without the re-read, a lost order would be lost for good. So the re-read passes back over recent orders and imports the missing ones — without ever creating a duplicate, since the identifier of every imported order is remembered.

One case deserves saying plainly: if your platform address is not a public HTTPS address, YouCan refuses the notification subscription. Orders still come in, but only through the re-read, so with a lag of a few minutes. That is the usual situation for a local installation.

What is left to do once connected

The connection removes the data entry, not the trade. What stays on your shoulders is exactly what made the work valuable before:

  • Selling prices — You set the price shown on YouCan. Profit is worked out from the total paid by the customer, less the product price, the confirmation fee and the delivery fee.
  • Confirmation — Leads enter the queue like any other lead. Either the confirmation team calls them, or you call them yourself — and in that case no confirmation fee applies.
  • Cities — A city typed freely into your store form is not always a city on the delivery list. It is matched automatically where possible, and settled during the call otherwise.
  • Damaged leads — Worth looking at daily in the early weeks: they state precisely what is wrong with the store configuration.
  • Access — If YouCan revokes access — password changed, application removed — the connection says so and asks you to reconnect. Orders from the gap are picked up by the re-read.

Connecting your YouCan store, step by step

  1. Align the SKUs

    Before anything else, open your YouCan products and give every variant the reference (SKU) of the matching product in the platform catalogue. This step decides whether your orders arrive usable or as damaged leads.

  2. Open Applications → YouCan

    In your seller workspace, the applications page lists the available order sources. If the YouCan connection says it is not configured, that is a platform-level setting rather than something on your account: write to support.

  3. Start 'Connect my store'

    You are redirected to YouCan, signed in to your merchant account. YouCan shows the permissions being requested: read orders, products, customers and store details, and manage subscriptions to order notifications.

  4. Accept, then come back

    Once authorised, YouCan sends you back to the platform. The store appears in the list of connections, and a matching store record is created so that every lead carries its origin.

  5. Check that real time is active

    The connection states whether the subscription to the "new order" event was accepted. If it was refused — which happens when the site address is not public HTTPS — orders will still come in, through a periodic re-read of the store.

  6. Link the fields if asked

    YouCan lets merchants customise their order form. If your fields do not carry recognisable names, the platform asks you to link them once. Orders that arrived in the meantime are not lost: they are replayed in order as soon as the mapping is saved.

  7. Place a verification order

    Order from your own store, using your own phone number. The lead should appear within the minute with the right item, the right total and the right city. You can put the connection in trial mode first: the lead is then marked as a test, follows the same calculation rules, but goes to no agent and counts in no figure.

Frequently asked questions about the YouCan connection

How long does a YouCan order take to arrive?
A few seconds when the real-time notification is active. If it is not — non-public address, subscription refused — the order arrives on the next re-read of the store, a few minutes later.
Do my YouCan products have to be catalogue products?
The product pages can be your own, with your photos and your copy. Only the reference matters: the SKU of the ordered variant must belong to a product you are allowed to sell. Without that, the order becomes a damaged lead.
Will my store be updated when the parcel is delivered?
No. The link reads orders, it writes nothing into YouCan: the order status in your store does not change. To be told about each stage, register an outgoing webhook pointing at an address of your choice.
Can I connect several YouCan stores?
Yes. Each store becomes a separate connection, with its own notification address, and leads keep a record of the store they came from. A store whose domain is already linked is reused rather than duplicated.
What happens if I disconnect the store?
The notification subscription is withdrawn at YouCan and no further order comes in. Leads and orders already created are untouched: they no longer depend on the store.
Does the test order count in my figures?
No, provided you set the connection to trial mode before ordering. The lead is then marked as a test: it follows the same rules and the same calculations, but it goes to no confirmation agent and appears in no report.
Why am I asked to link fields if this is an official integration?
Because YouCan allows merchants to customise their order form. Guessing the fields of an unknown form would produce wrong leads; the platform prefers to have you confirm the mapping once, then replay the orders it set aside.
Is an order cancelled in YouCan cancelled on your side?
No: the link imports the creation of an order, not its later changes. A lead that should no longer be processed is closed in the platform, either by you or by the agent during the call.

Also worth reading

Your YouCan orders, straight into the confirmation queue

One authorisation, matching SKUs, and every order arrives on its own — ready to be called, then delivered in one of the 65 cities served.

Sign up