Selling Cosmetics in Singapore: HSA Product Notification Guide

Confirm that the product and the notifying company fit the route

A product sold as skincare is not necessarily a cosmetic for Singapore regulation. The Health Sciences Authority (HSA) looks at its intended use and presentation. Its cosmetic regulatory overview excludes injections, eye drops, orally consumed products and products intended to treat conditions. Resolve a treatment claim or uncertain classification before choosing this notification route.

For an ordinary cosmetic, identify the Singapore business responsible for bringing it to market. HSA requires manufacturers and importers to notify before local supply. An overseas supplier's assurance that a similar item is already sold here does not establish your own filing position. An importer may need its own notification even when another Singapore company has notified the same manufacturer's product.

HSA's account route starts with a local entity registered with the Accounting and Corporate Regulatory Authority (ACRA). The underlying Singapore company registration requirements establish the business record; they do not establish that a particular formula, label or claim is compliant. Record which entity will contract with the supplier, hold the notification and respond to a safety issue.

Some supplies are excluded from notification, including specified promotional samples and research or development trials. The exclusion has conditions and does not remove ingredient, labelling or safety duties. A commercial launch should not be labelled a trial simply because the first shipment is small.

Build a product register that survives changes to the catalogue

The useful filing unit is not always your shop's SKU. A SKU may distinguish only a pack size, while a product range may contain shades or fragrances that require separate variant information. Use one register connecting each item to its label, manufacturer, responsible company and notification evidence. This is a launch-control tool, rather than a new HSA form.

The first three rows follow HSA's notification scope and variant rules ; the amendment rows follow its change and cancellation instructions . A formulation change also requires attention under the linked control guidance. Obtain the correct regulatory treatment before treating a reformulated item as an existing notification.

Notification identity and catalogue identity should be reconciled by someone who understands the product, not inferred from the warehouse code. Give each unresolved discrepancy an owner. A label approved internally for one entity or formula should not be released for a different one simply because the brand artwork looks similar.

Calculate HSA charges by product category and variant count

The HSA cosmetic fee schedule , checked on 16 October 2026, applies the same charges to notification and re-notification. For products applied around the eyes or on the lips, oral or dental care products, and hair dyes containing diamine compounds, a single product or each of the first three variants costs S$28. Other cosmetics cost S$13 on that basis. The fourth and subsequent variants cost S$8 each.

A qualifying range of four lip-product variants therefore has a displayed notification charge of 3 × S$28 + S$8 = S$92. Four unrelated products do not become a discounted range merely because they are sold in one shop. Confirm the presentation and fee category before using that calculation.

These are HSA transaction charges, not company-formation, testing, label-review or professional-service prices. Use the amount and payment options shown by the current service; HSA lists GIRO or eNETS. Reconcile the payment reference to the product register, and budget for the next annual notification separately.

The two preparation tracks must meet at the same product identity: company access makes submission possible, while product evidence makes the proposed supply defensible.

Submit through PRISM and verify the acknowledgement

HSA's linked notification procedure guide identifies the company, authorised representative, manufacturers, product presentation, declaration and payment as the filing data groups. The guide contains older interface instructions, so use it for preparation alongside the current service, rather than following obsolete browser or payment advice.

1. Settle product readiness. Review the formula against the current ASEAN Cosmetic Directive annexes and align the intended use, claims and packaging. Keep technical and safety material accessible to the responsible company.
2. Arrange account access. Use the local ACRA entity, establish Corppass authorisation and register the Client Registration and Identification Service (CRIS) company account. Check that the person doing the filing has submission authority, rather than draft-only access.
3. Enter the notification in PRISM, HSA's online regulatory system. Reconcile company and manufacturer details, product and brand names, and presentation or variants against the approved product register.
4. Review the declaration and transaction charge, complete the current payment and submission steps, and preserve the reference. Do not use a saved draft or a payment attempt as proof that notification succeeded.
5. Retain the generated acknowledgement and check the entity, product, notification number and validity dates. Return any discrepancy to the source data before releasing the affected item.

An acknowledgement is not HSA approval of safety or quality. HSA states that selling may begin on receipt of the acknowledgement, subject to the applicable product and supply requirements. It does not evaluate the cosmetic as part of this notification.

There is no single published lead time covering supplier documents, account preparation and a complete commercial launch. Successful submission generates the acknowledgement automatically; work backwards from product readiness and functioning access, rather than interpreting that automated endpoint as a guaranteed same-day launch.

For imported stock, the company’s first-shipment declaration arrangements belong to a separate workstream. Product notification does not replace the customs and controlled-goods checks applicable to the consignment.

Keep evidence current after the first sale

HSA's ASEAN Cosmetic Directive resources link the ingredient, safety and Product Information File guidance. Assign responsibility for obtaining these materials from the manufacturer and for keeping the current formula, label and supporting evidence connected. Confidential supplier data still needs a workable access arrangement when the authority requests information.

The cosmetic control guidance also connects product records to supply and safety follow-up. Preserve batch, customer, date and quantity information so an affected supply can be traced. Current HSA instructions require supply records for two years and call for reporting and recall action where safety issues arise.

Each notification lasts one year. Add its expiry and re-notification owner to the register, and reassess material changes before the next release. Use the correct amendment or new-notification route; if selling stops, follow the cancellation instructions rather than leaving the record unmanaged.

The responsible company needs control of more than a login. It needs a contact who can obtain evidence, reconcile stock and take action when a complaint, changed formula or expiry affects supply. If access or data is missing, resolve that specific gap instead of filing another unrelated product notification.

Release a cosmetic only when the product record and supply evidence agree

Approve launch when the item fits the cosmetic route, the responsible company is identified, its applicable acknowledgement is in place, and the formula, claims, label and traceability arrangements support supply. Record the evidence and approver for that release decision.

If a variant, importing entity or product identity no longer matches the filing, pause the affected item and determine the correct HSA action. Keep the unaffected catalogue separate in the register so one discrepancy does not disappear inside an apparently complete launch folder.