Docs for agencies

• Markup hooksThe data-blok and data-cast attributes that reliably identify a block or a part of the store, and what custom CSS may do on the page root.
• Blocks and fieldsEvery kind of page block and its fields: text, links, images and options.
• Website presetA website saved as a JSON file: theme, pages, store homepage, store layout and custom CSS. Plus the layout options and store templates.
• Webhooks and APIScoped API keys and signed webhooks for an ERP, a warehouse or Zapier.
• Partner frontendFrontend key, SDK, handing the cart over to checkout, the store look as files, the block schema, partner blocks and uploading a frontend: how to build a custom frontend for a client.

Getting started

1. Create a store or a website on the sign-up page. Your first store can be your own, just for trying things out.
2. As a programme partner who is the partner's contact person, you create a store for a client straight in the Partner portal: under Stores, the Create a shop for a client button takes the name, address, store type, market, a template from your library, the owner's e-mail and company, and your agreement to the terms. The store is created immediately, with no sign-up on the website and no verification e-mail. You can also create it through a link with your code: when signing up from the partner's contact address, choose “I am creating this store for a client” and enter the store owner’s e-mail. This creates a development store: customers cannot see it, nothing can be bought in it, no subscription is charged for it (AI features still draw on the credit here) and you browse it through a preview from the Subscription screen. Custom CSS is switched on in it from the start. An inactive store is put to sleep by the platform, and nothing in it is deleted; you can also put it to sleep yourself with Put the shop to sleep on the Subscription screen. A sleeping store does not count towards your limit of stores in progress.
3. The store owner gets an invitation to the Owner role as soon as the store is created and sees it from the start; you work in it as a Developer. When the store is ready, the owner opens it to customers on the Subscription screen: they check their company’s invoicing details, agree to the terms and start the subscription themselves. Create a store for a client on the market of the country where the owner’s company is based: the country does not change after the store is created.
4. As a partner you have the Partner portal at admin.portican.com: the stores Portican has assigned to you and their status, your codes with a sign-up link, recorded commissions by month with a Download CSV button, and the templates in your library. Portican gives you access with an invitation. Next to a code and a library template there stays a Create a shop for a client button that opens the sign-up page with your code, so that you can send the link to other people at the partner; a store for a client created from it comes only from the partner's contact address. The look of a store is saved as versions: on the Look versions screen you preview it, publish a version or go back to the previous one.
5. The admin runs at admin.portican.com. Under Shop › Look and feel you set the colours, fonts and corner radius, and the Basic or Expert website template with, for Expert, its style. A store with an online shop also gets 19 store templates there. A template sets the fonts, corner radius and colours, the homepage structure and the whole store layout; it takes over the brand colours only if you explicitly choose so, and never touches content, the logo or photos. Before you apply it, it shows what will change, and the previous look can be restored with one button. Some of the 17 store layout options can also be changed one by one in the Shop layout block. Templates and options, with their attributes, are covered in Website preset.
6. Build pages from blocks under Content › Website pages. A website has it from the start; a store turns it on for each market under Subscription and add-ons › Engines (the Website pages engine), and a published page with a menu position shows up in the store header and footer. A published page with an empty address replaces the store homepage, and a page cannot take the address of a store route (basket, checkout, product). Which blocks exist and which fields they have is covered in Blocks and fields.
7. Save a finished website or store as a file under Content › Website preset and use it as the starting point for your next client. A store without website pages saves and applies its design, homepage and store layout there, and its custom CSS too if you have the custom CSS permission; with website pages it brings the pages too, as drafts. The file format is described in Website preset. As a partner you can also save the design of a store you are building there with Save to my template library; you then apply a library template in your next store or create a store for a client with it.

What the platform allows and what it does not

• One store for everyone. Every client runs on the same build of the store. There is no custom template or code for a single client; you change the design and structure of a website through settings: the theme, the template, blocks and presets.
• No custom JavaScript in templates or blocks. A block carries text, links and options, and the store outputs them as text, never as HTML. A link that is not a safe URL is dropped by the platform.
• Tracking tags only through the measurement settings. They are connected under Marketing › Measurement and advertising, and only for the networks listed below. The store runs them according to the visitor's consent: before consent, Google receives only a cookieless signal (Consent Mode, advanced), and every other network starts only after consent to analytics or marketing.
• Google Tag Manager handles consent on its own. The container receives the consent state before it starts. Every tag inside it must have consent checks enabled (analytics_storage, ad_storage), otherwise it bypasses the consent banner; the platform cannot enforce that for you.
• Custom CSS only on top of hooks. With the Custom CSS Engine you write styles under Shop › Custom CSS. Every rule starts with a hook listed in Markup hooks; before the hook there may be the page root with the template, dark mode and store layout attributes, and the root on its own may change theme variables and define custom variables (Markup hooks). Images come only from the store's media library, and custom fonts (@font-face) are not accepted. Before anything goes live, the server cleans the styles and tells you the line and the reason for each finding; every save is a version with a preview. You can publish or switch off the styles on other markets of the store at the same time; when publishing, the same source is cleaned there and saved as a new version. Custom styles never apply to the checkout, sign-in, the customer account, legal pages or forms with personal data.
• You hear about it when custom CSS is switched off. When store staff or Portican switch it off in a store you brought in or are still building, everyone on your team with accepted access to the Partner portal receives an e-mail. If you switch it off yourself, no e-mail is sent.
• Checkout, sign-in and the customer account have no hooks. Where customers type a password or pay, the platform's own design applies.
• The platform does not write legal texts. Terms and conditions, the privacy policy and the returns policy each have their place in the store; the merchant adds the wording with their own lawyer.

Measurement networks the store can connect

• Google Tag Manager analytics
• Google Analytics 4 analytics
• Microsoft Clarity analytics
• Google Ads marketing
• Meta (Facebook, Instagram) marketing
• ChatGPT ads marketing
• TikTok marketing
• Pinterest marketing
• LinkedIn marketing
• Microsoft Advertising marketing
• Sklik (Seznam) marketing
• Google Customer Reviews marketing
• Ecomail (newsletter) marketing

From the platform code. This list is built directly from the platform source code, and every deployment checks that the two still match.

How to report a bug

Email info@portican.com. We can fix a bug faster when your message includes:

• the address of the page where the bug appears,
• when it happened, with the date, time and time zone,
• what you expected and what happened instead,
• a screenshot, the browser and the device,
• for a hook, its value; for a preset, the file you used.

A hook from the list that is missing from a page, or sits somewhere other than its description says, is a platform bug. Please report it.