Professional Documents
Culture Documents
Site Administration US_BEC_003 System Access Control - Roles & Access Rights
Site Administration US_BEC_004 Business User Access Control - General Info
Site Administration US_BEC_005 Business User Access Control - Organization & Role Info
Site Administration US_BEC_006 Business User Access Control - Site Access Info
Site Management US_BEC_011 Business User Site Level Properties - Shipping Method
Site Management US_BEC_012 Business User Site Level Properties - Tax Component
Site Management US_BEC_013 Business User Site Level Properties - Shipping Method -
Prioritization
Site Management US_BEC_014 Business User Site Level Properties - Payment Method
Site Management US_BEC_015 Business User Site Level Properties - Payment Method -
Prioritization
Site Management US_BEC_016 Business User Site Level Properties - Order Quantity
Restriction
Site Management US_BEC_017 Business User Site Level Properties - Order Value
Restriction
Site Management US_BEC_018 Business User Additional Services (Enable / Disable)
Catalog Management US_BEC_048 Business User Manage Orderable Quantity - Item Level
Catalog Management US_BEC_049 Business User Import of Delta Update Feed
2) Manager - Users who perform activities such as reviewing and approving content
created by an EPub-User. An EPub-Manager can also deploy assets to production
targets.
1) These roles represent typical Business Control Center users and simplify the
process of creating internal users
- Internal User Administration
---- Internal Users Full Access
- Merchandising
---- Site Catalogs Full Access
---- Media Full Access
---- Price Lists Full Access
---- Preview Users Full Access
---- Site Administration Read-Only Access
---- SEO Tags Full Access
---- Store Locations Full Access
- Promotions User
---- Promotions Standard User Access
- Promotions Administrator
---- Promotions Full Access
- Personalization
---- Targeting & Segmentation Full Access
---- Site Catalogs Read-Only Access
---- Media Read-Only Access
---- Site Administration Read-Only Access
---- External Users Full Access
---- Preview Users Full Access
- Site Administration
---- Site Administration Full Access
---- Site Catalogs Full Access
---- Price Lists Full Access
---- Preview Users Full Access
1) The general info below holds information such as the username, password, e-mail,
etc associated with the user
2) The system must allow the business user to manage the following information:
- Login
--- Username
--- Change Password
- Basic Info
---- First Name
---- Last Name
---- E-mail
1) The organizational & role info below lists out roles delegated to the selected user
and which organization they are associated to
2) The system must allow the business user to manage the following information:
- Organizations
--- Inherited Organization
--- Organizations
--- Primary Organization
- Roles
--- Inherited Roles
--- Additional Roles
1) The Site Access info below determines to which sites the user is granted access
permissions
2) The system must allow the business user to manage the following information:
- Overview
--- Display Name
--- Access Level
--- Source
- Full Access
--- Full Access Site Groups
--- Full Access Sites
- Read-Only Access
---- Read-Only Access Site Groups
---- Read-Only Access Sites
1) The business user should be allowed to create a site and specify the following:
- Site Name
- Description
- Site Category
2) Business users to have the capability to register and configure Web sites in a
multisite setup
1) Business user to configure shipping methods at a site level
2) They must provide the following information for a given shipping method:
- Delivery Option (Ship To An Address / In-Store Pick)
- Shipping Method (The shipping method property is the shipping method code used
by the backend fulfillment system and is a mandatory field)
- Shipping Method Name for Dynamic Tagging Management
- Shipping Name (The shipping name property is the shipping method display name
in the frontend)
- Shipping Amount
- IsActive (The isActive property determines whether the shipping method can be
displayed in the frontend or not)
- IsDefault
1) Business user should have the capability to manage & configure tax component
for a given site
1) Business user to control the order in which shipping methods would render in the
storefront via the 'Priority' property
2) Business user should be able to drag and drop and change the priority of shipping
method configured
1) Business user to configure payment methods at a site level
2) They must provide the following information for a given payment method:
- Payment Method Name
- IsEnablede (The isEnabled property determines whether the payment method can
be displayed in the frontend or not)
- IsDefault
1) Business user to control the order in which payment methods would render in the
storefront via the 'Priority' property
2) Business user should be able to drag and drop and change the priority of payment
method configured
1) Business user can specify a max quantity limit and restrict end user from
ordering items in large quantities
1) Business user can specify a max order value limit and restrict end user from
placing a large value order
1) Business user should have the capability to enable disable site specific
capabilities, e.g.:
- In-Store Pickup (Enable / Disable)
- PayPal (Enable / Disable)
Post-Conditions:
1) Catalog definition is ready to consume the initial catalog import feed
Assumptions:
1) Business has provided category classifications along with intended hierarchy and
the same has been configured in the master catalog
2) Sub category under relevant parent categories have been configured in the master
catalog
3) Business has provided a list of product types and their relevant attributes and all of
this has been defined as a part of the master catalog
Acceptance Criteria
1) Category and sub categories have been defined in the master catalog.
2) Products and SKUs have been defined against each category / sub categories.
4) SKU attributes associated to products have been defined in the master catalog.
6) System must consider staged and online catalog versions for the catalog.
1) System must allow the business user to create a project and manage their
assets
2) System must allow multiple business users to create project(s) in their own
workspace
3) The system must maintain the following attributes for a given project:
- Project Name - shows the name assigned to this project
- Project Status - shows the project’s current status, one of the following:
---- Active Project: The project is currently available to be worked on. The task
that triggers deployment remains outstanding.
---- Project Complete: Project assets are deployed (or await deployment) and
the project cannot be changed.
- Creator - shows name of the person who created the project in the BEC
- Start Date - shows the project’s creation date
4) System must allow the business user to view existing project and delete them
as well
1) The system must allow the business user to manage their changes across
assets within a given project. E.g. Merchandising Updates such product
enrichment, promotions, content changes, etc.. Note: Asset association to a
project should happen in an automated manner
2) The system must allow the business user to perform the following:
- View Asset
- Edit Asset
- Deploying Assets
- Versioning Assets
- Remove Assets
1) The system must allow the business user to preview project assets to see how
they behave and look on a Web site. For example, you can preview how an
article displays with a specific stylesheet.
3) The system must allow the business user to preview assets from the
perspective of different user profiles; they can also view them on more than one
site if multiple sites are configured
1) The system must create an version of the asset the business user has intiated
to work on / introduce change(s) in a given project
2) The system must allow the business user to view revisions being made
3) The system must allow the business user to restore the asset to a previous
version
Note: Restoring does not delete any data; it replaces the active version with the
restored version. All versions will continue to reside in the repository
1) The system must allow the business user to deploy project assets after the
appropriate task in the project is complete assuming the business has
acknowedged the changes made after previewing them
2) All deployments must happen to the staging site and then the business user
should have an option to deploy changes to production
3) To carry out the deployment process, the business user must ultimately
deploy the proejct the assets reside in
1) The system must maintain logs and track all activities carried out in BEC
Assumptions
1) Categories & Sub Categories that have been imported from the source
system during initial data load / delta feed.
Acceptance Criteria
1) Any updates made to category/sub category properties by business user
must reflect in targeted environment after deployment
3) The products not associated with any other category will be orphaned and
will not display on site
Assumptions
1) Variants would be grouped under products by the source system
Acceptance Criteria
1) The system must allow the business user to manage variants. Basically, make
modifications to attributes that are not read-only.
2) There is a possibility that some of these variants are not coming from the correct
family, the business user would eventually manually map them to the correct family.
3) In some cases, a product can belong to multiple families. Hence, any changes
made to the base product must reflect across families they are associated to
Assumptions
1) Variants would be grouped under products by the source system
Acceptance Criteria
1) The system must allow the business user to manage variants. Basically, make
modifications to attributes that are not read-only.
2) There is a possibility that some of these variants are not coming from the
correct family, the business user would eventually manually map them to the
correct family.
3) In some cases, a product can belong to multiple families. Hence, any changes
made to the base product must reflect across families they are associated to
1) The system must not create duplicate copies of a given product if exists in
the catalog during bulk updates.
2) The system must affect only those attributes that are mentioned in the bulk
update file.
3) If fields are left blank in the file that is to be uploaded will not have an
impact on existing catalog data, no updates would occur.
5) The system must log exception(s) if encountered and must notify the
assigned business user via an e-mail
1) Deployment entails receiving all updated assets, hierarchy, etc
2) Business user can provide a title to the cross-selling slot, there should be a
provision to enter localized content based on the no. of languages the site is
supporting.
3) Business user to define settings of the product reference component such as:
- Name
- Catalog Version
- Enable / Disable visibility
- Manage product reference types – Either similar products or products that
would go with the parent product
- Maximum no. of products that need to render
1) Business user should be able to hide a few categories, they should be able to
control the visibility of the category.
2) Business user can create hidden categories for different sites.
1) Business user should be able to exclude category at the following level:
a. Site Level
b. Customer Level
c. Promotion Level
2) Business user should be allowed to exclude multiple categories in any of the above
list by comma separating the product id(s)
1) Business user should be able to exclude products at the following level:
a. Site Level
b. Customer Level
c. Promotion Level
2) Business user must set the 'OnHold' flag at the product level to ‘TRUE’ if it
does not qualify to render in the storefront
3) Business user must set the 'OnHold' flag at the product level to ‘FALSE’ if it is
eligible to render in the storefront
4) Changes made to the 'OnHold' flag of a given product will reflect across
site(s) unless otherwise specified in product exclusions
1) Single Product Image is the largest image and refers to the main/featured image
on your individual product details page.
2) Catalog Images are medium-sized images appearing in product loops, such as the
Shop page, Product Category pages, Related Products, Up-sells, and Cross-sells.
3) Product thumbnails are the smallest images used in the Cart, Widgets, and
(optional) Gallery thumbnails underneath the Single Product Image.
Assumption
1) The primary image of a product to be displayed in the product list page is
different from the one the business user will configure for the product details
page
Acceptance Criteria
1) Business user can manage the order in which the alternate images must
appear
3) The order defined will be followed for the product details pages for all sites
4) If the order is not provided, the default order (as received during the initial
catalog feed / delta update(s)) is assigned to the image(s)
2) Business user can only modify values of category / product / SKU attributes
that are not read-only
1) Allow new products to be automatically uploaded in the BEC and available for BEC
users to merchandise without manual intervention
1) Business user to determine when a product is qualified to display in the
storefront based on certain attribute(s) definitions, e.g.:
- Image
- Equity
- Inventory
- Price
and if the product 'On Hold' = true
1) Business users to manage the below properties at the product level, e.g.:
- WebExclusive
- New Arrivals
- Clearance
2) Business users to have the capability to override any of the above properties
1) Business users to have the ability to associated / group products that share
the same tags or categories
3)
2) This is to ensure that the product can still be purchased even if it's inventory is '0'
2) This is to ensure that the product can be purchased even if its not available online
as yet
1) Business user to configure the permissable quantity a given SKU can be
ordered for a given order
Assumptions
1) Import periodic catalog updates at attribute level from source system.
3) The delta update feed would run once in a day, this would be a nightly feed
Acceptance Criteria
1) Catalog delta updates feed file should have mapping attributes in order to
populate updated source information to the target master catalog
2) This would determine the display of updated product information on the site
3) Business users would have to the capability to edit any attributes that are not read-
only
5) Changes made to the catalog from any site must reflect across all sites
6) Additional categories / products / SKUs can also be a part of the delta feed
updates
2) Business user must provide the following information in the 'Condition' section:
- No. of Items to Buy - How many items the customer must purchase in order to
receive the discount. This quantity must be at least 1
- Item(s) to Buy - If you do not want the promotion to apply to all purchases, specify
the categories, products, etc. that qualify. You can add additional criteria as needed
and combine them in either AND (the purchase must meet all criteria) or OR (the
purchase must meet at least one criterion) form
3) Business user must provide the following information in the 'Offer' section:
- Number of items to discount - For a traditional “buy one, get one” promotion, enter
1; for each item the customer purchases, one item is discounted. You can discount
any number of items, however, or check Unlimited to apply the promotion to all
items once the promotion condition has been met
- Apply Discount To - Select whether the discount should be applied to the lowest or
the highest priced items in the order first
- Item(s) to Discount - Use the selection boxes to identify items that qualify for the
discount
- Discount Type - Select amount off, percentage off, fixed item price, or free
- Discount - Enter the amount of the discount or, if the Discount Type is Fixed Item
Price, enter the price of the item. If the Discount Type is Free, this field is disabled
2) Business user must provide the following information in the 'Condition' section:
- No. of Items to Buy - How many items the customer must purchase in order to
receive the discount. This quantity must be at least 1
- Item(s) to Buy - If you do not want the promotion to apply to all purchases, specify
the categories, products, etc. that qualify. You can add additional criteria as needed
and combine them in either AND (the purchase must meet all criteria) or OR (the
purchase must meet at least one criterion) form
- Item(s) to Exclude - To exclude items from the condition (that is, they won’t help the
customer qualify for the promotion), click the Add Criteria button under the Items to
Exclude area
3) Business user must provide the following information in the 'Offer' section:
- Number of items to discount - You can discount any number of items, or check
Unlimited to apply the promotion to all items once the promotion condition has
been met
- Apply Discount To - Select whether the discount should be applied to the lowest or
the highest priced items in the order first
- Item(s) to Discount - Use the selection boxes to identify items that qualify for the
discount
- Discount Type - Select amount off, percentage off, fixed item price, or free
- Discount - Enter the amount of the discount or, if the Discount Type is Fixed Item
Price, enter the price of the item
1) Business user to create following item level promotions:
a. Buy Within Specified Time Frame Get Item Discount
2) Business user must provide the following information in the 'Condition' section:
- Buy Between Dates - Specify the start and end dates for the condition
3) Business user must provide the following information in the 'Offer' section:
- Number of items to discount - You can discount any number of items, or check
Unlimited to apply the promotion to all items once the promotion condition has
been met
- Apply Discount To - Select whether the discount should be applied to the lowest or
the highest priced items in the order first
- Item(s) to Discount - Use the selection boxes to identify items that qualify for the
discount
- Discount Type - Select amount off, percentage off, fixed item price, or free
- Discount - Enter the amount of the discount or, if the Discount Type is Fixed Item
Price, enter the price of the item
2) Business user must provide the following information in the 'Condition' section:
- No. of Items to Buy - How many items the customer must purchase in order to
receive the discount. This quantity must be at least 1
- Item(s) to Buy - If you do not want the promotion to apply to all purchases, specify
the categories, products, etc. that qualify. You can add additional criteria as needed
and combine them in either AND (the purchase must meet all criteria) or OR (the
purchase must meet at least one criterion) form
- Item(s) to Exclude - To exclude items from the condition (that is, they won’t help the
customer qualify for the promotion), click the Add Criteria button under the Items to
Exclude area
3) Business user must provide the following information in the 'Offer' section:
- Number of items to discount - Enter the number of items that can receive the
discount, or check Unlimited. For instance, if a customer purchases six items in the
discounted category, you might discount five of them
- Apply Discount To - Select whether the discount should be applied to the lowest or
the highest priced items in the order first
- Item(s) to Discount - Use the selection boxes to identify items that qualify for the
discount
- Discount Type - Select amount off, percentage off, fixed item price, or free
- Discount - Enter the amount of the discount or, if the Discount Type is Fixed Item
Price, enter the price of the item
1) Business user to create following item level promotions:
a. Spend Y Get Item Discount
2) This promotion discounts a particular item or items when a customer spends the
specified amount. First, specify the Spend threshold for the condition
3) Optionally, you can define a promotion upsell for the promotion. This allows your
site to inform customers when they are close to qualifying for the promotion. Bear in
mind that the upsell does not appear on your site automatically, but must be
incorporated into a JSP or otherwise actively presented to the customer
4) If you specify a promotion upsell as part of the condition and offer, you can still
specify additional upsells under the Promotion Upsells. Note that the promotion
upsell section only appears in the condition and offer template when you first create
the promotion. To edit a promotion upsell, use the Promotion Upsells section of the
promotion
1) This promotion discounts an entire order when the customer places the order
within the specified time period.
2) First, specify the start and end dates for the condition. In the case of this
promotion, these fields are the equivalent of the usage start and end dates; if you
change one set of dates, the other set updates automatically.
2) First, specify the start and end dates for the condition. In the case of this
promotion, these fields are the equivalent of the usage start and end dates; if you
change one set of dates, the other set updates automatically.
1) Gift with purchase promotions are a special promotion type that allows you to give
customers a free item as part of their order
2) Free gift criteria can be specified as any of the following asset types:
- SKU
- Product
- Category
3) SKU bundles cannot be used as gift items
All Promotion types (Item, Order, Shipping) are combinable. Eligible offers will be
evaluated by the promotions engine and then applied to the order based on
promotion eligiblity and the priority ranking assigned to the offer during promotion
setup.
1) System should allow the business user to manage the following information
related to stores:
- Store Name
- Address Line 1
- Address Line 2
- City, State, Zip Code
- Working Hours
- Telephone No.
- Email Address
2) System should also have the capability to import store data from an external
system
3) System must allow the business user to view / edit / delete stores at a site level
4) System must provide a list view and details view of store data, E.g.: List View would
consist of only store name and location, where as details view would display all
attribtues related to store data