The panel builds a .wgt signed with your own Samsung certificate pair, which you generate in Tizen Studio. You register the app in Seller Office, upload the package and the store assets, and request certification. Plan around two constraints: a new seller launches in the US only, and certification runs for weeks.
Distribution scope: Seller Office admits new members as public sellers, and a public seller's apps can launch in the United States only. Any other country requires partner status, which Samsung grants through its regional content teams.
The author certificate is permanent. Samsung verifies every update against the author certificate of the first release, and a package signed by any other author is refused. Keep an offline backup of the .p12 and its password for the life of the app.
Signing locally instead? With no certificates on file, the Samsung build returns the Tizen source (.zip) for you to package and sign in Tizen Studio.
Frequent rejection causes: Back-key handling and incomplete test details. The template implements Samsung's Back rules (up one level, exit dialog on Home, long presses ignored), which leaves the test details as the part to get right.
Rebuild Samsung in the panel with the original author certificate still on file, upload the new .wgt as a new version, and request certification again. Videos, logo and links come from the feed and need no new version.