Start here
Getting started with LynkPIM
Follow the complete path from account setup to your first reviewed product and channel export.
For workspace users and administrators · Updated October 1, 2026
What this module is for
Follow the complete path from account setup to your first reviewed product and channel export.
Use this page when you need to complete the task yourself and understand what each action changes. The steps name the relevant screen, explain why the action belongs in the workflow, and state what to verify before moving on.
Before you start
- Sign in with a role that can view or change the records in this guide.
- Have the product, file, channel, or workspace information ready before starting an action that saves data.
- Use a small test record or file first when an action affects multiple products or a connected channel.
1. Create and verify the workspace
Complete these actions in order. They describe the screen to use, the decision to make, and the evidence to check before you move to the next stage.
-
Step 1.1
Do this: Open Sign up, enter the requested account and organization details, then submit the form.
Why this matters: This keeps the create and verify the workspace work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Look for a confirmation message, a newly created record, or a job status entry. If nothing changes, read the inline field error or job detail before retrying.
-
Step 1.2
Do this: Use the verification link sent to your email. If setup is interrupted, sign in and use the resume screen to continue.
Why this matters: This keeps the create and verify the workspace work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Confirm that the named screen or panel is visible and contains the expected values. If a control is missing, check your workspace role before continuing.
-
Step 1.3
Do this: Complete the onboarding checklist, invite teammates when prompted, and open the dashboard after setup finishes.
Why this matters: This keeps the create and verify the workspace work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Confirm that the named screen or panel is visible and contains the expected values. If a control is missing, check your workspace role before continuing.
2. Build the first catalog flow
Complete these actions in order. They describe the screen to use, the decision to make, and the evidence to check before you move to the next stage.
-
Step 2.1
Do this: Create categories, attributes, and a product family before importing a large catalog.
Why this matters: This keeps the build the first catalog flow work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Look for a confirmation message, a newly created record, or a job status entry. If nothing changes, read the inline field error or job detail before retrying.
-
Step 2.2
Do this: Add one product and its variants, attach media, and review the product’s Quality and SEO tabs.
Why this matters: This keeps the build the first catalog flow work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Look for a confirmation message, a newly created record, or a job status entry. If nothing changes, read the inline field error or job detail before retrying.
-
Step 2.3
Do this: Connect a channel, check its required fields, then use a workflow or change request to review the product before export.
Why this matters: This keeps the build the first catalog flow work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Look for a confirmation message, a newly created record, or a job status entry. If nothing changes, read the inline field error or job detail before retrying.
3. Confirm the result
Complete these actions in order. They describe the screen to use, the decision to make, and the evidence to check before you move to the next stage.
-
Step 3.1
Do this: Open Quality > Issues Queue to resolve missing data.
Why this matters: This keeps the confirm the result work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Confirm that the named screen or panel is visible and contains the expected values. If a control is missing, check your workspace role before continuing.
-
Step 3.2
Do this: Run a small export and review its job status and output before scheduling recurring delivery.
Why this matters: This keeps the confirm the result work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Look for a confirmation message, a newly created record, or a job status entry. If nothing changes, read the inline field error or job detail before retrying.
-
Step 3.3
Do this: Use Reports to monitor quality and search signals after the pilot is live.
Why this matters: This keeps the confirm the result work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Confirm that the named screen or panel is visible and contains the expected values. If a control is missing, check your workspace role before continuing.
Events and statuses to watch
Actions such as saving, importing, exporting, connecting, publishing, and approving can either update a record immediately or create background work. Wait for the on-screen confirmation and then check the relevant list, detail view, or job status before repeating an action.
- Saved or created: confirm the record appears with the intended values.
- Queued, running, or processing: wait for completion and open the job or event detail if progress stops.
- Failed, partial, rejected, or blocked: read the specific message, correct the source data or permissions, then retry only the affected work.