## Starting from Package Pages to Compare ERP Options
When you begin evaluating ERP choices in **Sherkety ERP & Website Platform**, the most useful starting point is usually a **package page**. These pages bring together a broader offer in one place so you can judge whether it fits your business before you spend time opening individual module pages.

On a package page, focus first on the parts that help you make a quick decision:

- **Package name** so you can tell one offer from another
- **Included apps or modules** such as **Accounting**, **HR**, **Sales & CRM**, **Purchasing**, or **Reporting**
- **Pricing area** that shows the package cost or pricing tier
- **Feature highlights** that summarize what the package is designed to support
- Action buttons such as **Start Trial**, **Contact Sales**, **Request Demo**, or **View Details**

These package pages work as a top-level entry point. Instead of comparing every ERP capability one by one, you can first answer bigger questions:

- Does this package cover the main business areas you need?
- Is the visible price range close to your budget?
- Does the offer look like a complete bundle or a smaller starting package?

[SCREENSHOT: ERP package page showing package name, included modules, pricing block, and action buttons]

This is different from opening a single module page. A package page helps you judge **broad fit**. A module page helps you inspect one capability in detail, such as whether **Accounting** includes the finance tools you expect or whether **Sales & CRM** matches your sales process.

If you already reviewed module detail journeys in [Evaluating ERP Modules From Catalog to Detail Pages](doc:evaluating-erp-modules-from-catalog-to-detail-pages), treat package pages as the layer above that process. Start wide with the package, then drill down only into the modules that matter most to your buying decision.

## Browsing App Listings to Narrow Down What You Need
After reviewing a package page, the next useful move in **Sherkety ERP & Website Platform** is opening the **ERP apps catalog** or app listing view. This is where broad package interest turns into a more focused review of individual apps and modules.

From the listing page, use the visible controls to narrow what you see:

- **Category navigation** to move into areas like **Accounting**, **Sales & CRM**, **HR**, **Purchasing**, or **Reporting**
- A **search box** to look for a specific capability by name
- **Filters** or **tags** to reduce the list to more relevant options
- **Sort options** to change the order of results

These controls are especially helpful when a package page mentions several included areas but you want to inspect only one or two of them more closely.

Each app card usually gives you a quick decision snapshot. Look for details such as:

- **App name**
- **Short description**
- **Publisher or vendor**
- **Rating, popularity, or other trust indicators** if shown
- Buttons or links such as **Learn More**, **View Details**, or similar actions

[SCREENSHOT: ERP apps catalog with category menu, search field, filters, and app cards]

This listing view helps you answer an important buying question: is the package built around core modules that are already part of the main ERP offer, or does it depend on extra apps to fill gaps? If you see a business need on the app listing but not clearly named on the package page, that is a sign to investigate further before assuming it is included.

Use the app listing to compare several cards side by side. For example, you might check whether your shortlist covers **finance**, **sales**, **people management**, and **reporting** without needing too many separate add-ons. This makes the app listing a practical bridge between package-level browsing and detailed module evaluation.

## Opening Module Entry Points to Inspect Specific Capabilities
A **module entry point** in **Sherkety ERP & Website Platform** is the dedicated page for one ERP capability. Examples include pages for **Accounting**, **Sales & CRM**, **HR**, **Purchasing**, and **Reporting**. These pages are where you move from general package comparison into feature-level inspection.

When you open a module page, review the visible page elements carefully:

- The **module title**, which confirms exactly what area you are viewing
- The **feature summary** or scope description, which explains what that module covers
- **Screenshots** or visual sections that show the type of work the module supports
- Any notes about **package requirements**, **availability**, or related modules
- Links or navigation back to the broader **ERP apps catalog**, **ERP system page**, or package-related pages

[SCREENSHOT: Module page showing title, feature highlights, screenshots, and navigation trail]

These pages are useful because they help you verify what is actually available. A package page may tell you that a business area is supported, but the module page helps you see whether that support is:

- **Included as part of the main offer**
- Available as an **optional add-on**
- Limited to a **higher package or edition**

This is also where navigation labels matter. If the page header, menu trail, or breadcrumb shows how the module sits inside the wider ERP offering, you can tell whether you arrived from the **ERP system** area, the **apps catalog**, or another package-related path. That context helps you avoid mixing up a core module with a separate add-on.

Use module entry points when you need confidence about one business function. If your team cares most about payroll, sales pipeline, purchasing approvals, or reporting dashboards, these pages give you the clearest place to inspect those capabilities before contacting the sales team.

## Comparing What Is Included Across Packages, Apps, and Modules
To compare ERP options properly in **Sherkety ERP & Website Platform**, it helps to think of the discovery journey in three layers:

- **Package pages** show the overall offer
- **App listings** show the available apps or modules individually
- **Module pages** show the detailed capability for one area

Using all three together makes it easier to tell what is bundled and what may need to be added separately.

Start with the package page and note the **included modules list**. Then open the app listing and check whether the same business areas appear as individual app cards. Finally, open the module pages for the areas that matter most and look for notes that clarify access, scope, or package fit.

Pay close attention to these comparison points:

- **Included modules** shown directly on the package page
- **Optional add-ons** that appear in the app listing but are not clearly listed in the package
- **Edition or tier restrictions** if one capability belongs to a higher offer
- **Pricing differences** between package-level pricing and module-level availability
- **Feature availability** across packages, especially for finance, inventory, sales, HR, and reporting

[SCREENSHOT: Side-by-side comparison notes from package page, app listing, and module page]

This process helps you spot overlaps and gaps. For example, two pages may both mention reporting, but one may refer to built-in dashboards while another points to a separate analytics-focused module. In the same way, a package may mention sales support broadly, while the module page shows whether **Sales & CRM** includes the specific workflow your team needs.

A practical shortlist should cover your required business areas clearly. Before moving forward, confirm that your preferred option represents the core functions you need:

- **Finance or Accounting**
- **Inventory or Purchasing**
- **Sales or CRM**
- **HR**
- **Reporting**

If one of these appears only as a separate app and not as part of the package, treat that as a comparison point rather than an assumption.

## Using Entry Points to Judge Product Fit Before Contacting Sales
Before you use **Contact Sales**, **Request Demo**, or **Start Trial** in **Sherkety ERP & Website Platform**, use the available entry points to build a clear picture of fit. This saves time and helps you ask better questions.

Begin with the **package page**. This is the fastest place to confirm two things:

- Whether the package appears to cover your main business areas
- Whether the visible pricing or tier looks realistic for your budget

If the package page looks promising, move to the **ERP apps catalog**. There, check whether the capabilities you care about appear as core ERP apps or as separate additions. This matters because a package can look complete at first glance, while the app listing may reveal that some functions are handled through extra apps rather than the main included modules.

Next, open the **module pages** for your highest-priority areas. On each page, look for boundaries such as:

- Notes showing a module belongs to a specific package
- Signs that a capability is optional rather than standard
- Limits in the feature description that narrow what the module actually covers

[SCREENSHOT: Buyer reviewing package page, app card, and module detail page before clicking Contact Sales]

As you review, keep a simple record of what you checked. Capture the exact:

- **Package names**
- **App names**
- **Module pages**
- Visible pricing references
- Any notes about inclusion or package level

This gives you a concrete starting point when you reach out. Instead of saying you are “interested in ERP,” you can refer to the package and modules you already reviewed. That makes the conversation more specific and helps the sales team respond to your actual business needs instead of broad interest.

## Avoiding Common Confusion When Exploring ERP Offerings
When comparing ERP options in **Sherkety ERP & Website Platform**, most confusion comes from mixing package information, app listing details, and module-specific notes. You can avoid that by checking where each piece of information appears.

If a feature shows up on an **app card** but not on the **package page**, do not assume it is included. Treat it as a possible **optional add-on** until the package details or module page clearly confirm otherwise. This is one of the most common places buyers overestimate what is bundled.

If two modules seem to cover the same business process, compare the wording on each page. Look at the **module title**, the **short description**, and any package-related notes. One page may describe the core business function, while another may describe an extension or a more specialized area.

Pricing can also be misleading if you do not check the source. Make sure you know whether the visible amount belongs to:

- The **overall package**
- An **individual app**
- A **higher-tier offer** required to access that module

[SCREENSHOT: Example of package pricing area and separate app or module detail section]

Navigation clues can help when you lose track of where a page fits. Use:

- **Breadcrumbs**
- Links back to the **ERP apps catalog**
- Links to the **ERP system** page
- Package-related **View Details** actions

These elements help you trace the correct discovery path and understand whether you are looking at a broad offer, an app listing, or a single module page.

If something still feels unclear, compare the same capability across all three levels rather than relying on one page alone. That extra check often reveals whether a feature is standard, optional, or tied to a different package than the one you first opened.

## Overview
In **Sherkety ERP & Website Platform**, ERP discovery usually starts from one of three visible entry points:

- A **package page** that groups modules under a pricing tier or bundle
- The **ERP apps catalog** where individual apps are listed
- A dedicated **module page** such as **Accounting**, **HR**, **Sales & CRM**, **Purchasing**, or **Reporting**

Each entry point serves a different purpose. **Package pages** are best for early comparison because they show broad coverage, pricing context, included modules, and action buttons like **Start Trial**, **Request Demo**, or **Contact Sales**. **App listings** help you narrow your focus using **search**, **categories**, **filters**, and app cards. **Module pages** let you inspect one capability in more detail through feature descriptions, screenshots, and package-related notes.

Use these entry points together rather than separately:

- Start on a package page to judge overall fit
- Move to the app listing to see what is available individually
- Open module pages to confirm what each area actually covers

This document focuses on how those discovery paths connect. For broader ERP browsing, see [Discovering ERP Products and Packages](doc:discovering-erp-products-and-packages), [Browsing the ERP Apps Catalog](doc:browsing-the-erp-apps-catalog), and [Using ERP System Landing Pages to Evaluate Offerings](doc:using-erp-system-landing-pages-to-evaluate-offerings).

If you want a deeper module-by-module review flow, continue using the approach from [Evaluating ERP Modules From Catalog to Detail Pages](doc:evaluating-erp-modules-from-catalog-to-detail-pages). The goal here is simpler: understand where to start, how to move between package, app, and module views, and how to avoid confusing a broad offer with a single capability page.

## Prerequisites
You do not need an account to follow this discovery workflow in **Sherkety ERP & Website Platform**, but it helps to arrive with a short list of business needs. That way, the package pages, app listings, and module pages are easier to compare.

Before you begin, make sure you can already do the following:

- Browse public ERP pages and move through the main website navigation
- Open the **ERP system** area and the **ERP apps catalog**
- Recognize common actions such as **View Details**, **Start Trial**, **Request Demo**, and **Contact Sales**
- Use page structure cues like **breadcrumbs**, section headings, and comparison blocks

These related guides can help if you need a quick refresher:

- [Navigating Public Pages and Entry Points](doc:navigating-public-pages-and-entry-points)
- [Using Header Menus and Footer Links](doc:using-header-menus-and-footer-links)
- [Understanding Breadcrumbs and Page Location](doc:understanding-breadcrumbs-and-page-location)
- [Exploring ERP App Categories and Module Entry Points](doc:exploring-erp-app-categories-and-module-entry-points)

It is also useful to prepare a simple checklist of the business areas you must cover, such as:

- **Accounting**
- **Sales & CRM**
- **HR**
- **Purchasing**
- **Reporting**

As you browse, compare every package and module against that list. If a needed area appears only in the app listing and not on the package page, mark it for closer review.

From here, the next guide is [Comparing Website and ERP Offers for Business Needs](doc:comparing-website-and-erp-offers-for-business-needs), where you will use what you found on package pages and module entry points to decide which offer best matches your business priorities.