10.46243/jst.2027.v2.i02.pp49-60 registered
Impact of Customer Relationship Management in Retailing Sector -With Special Reference to Big Bazaar-An Empirical Evidence.
Resolves to https://www.jst.org.in/index.php/pub/article/view/197
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jst.2027.v2.i02.pp49-60
Registered 29 Sep 2026 via crossref · record version 2 · last change 29 Sep 2026, 11:59 PM · record sha256 c4d8d412ae695a97…
Resolve ⬇ Record (JSON) ⬇ Kernel Metadata Declaration (XML) Compare with Crossref Cite (APA · BibTeX · RIS · CSL)
What the DOI identifies
JournalArticle — an article in a journal · Digital · Visual · en
Impact of Customer Relationship Management in Retailing Sector -With Special Reference to Big Bazaar-An Empirical Evidence. (PrincipalTitle)
Published 2017-03-01
Part of Journal of Science & Technology · ISSN 2456-5660 · volume 02 · issue 02 · pages 49–60
Agents
- Dr.Zia Ur Rehman (author)
- P.Anupama (author)
- N. Krishnaveni (author)
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jst.2027.v2.i02.pp49-60
Abstract
In today’s first-paced competitive business environment it’s more important than ever to create and maintain long-losing business relationships. Today, Customer Relationship Management (CRM) manages business process spanning sales, support, and marketing creating effective customer interactions. Given the purpose of CRM, the functionality is straightforward, and the benefits of successful deployments clearly generate value and profitability for any company. Grate CRM solutions need to encourage users to interact with the application as well as be in-tune with the business and IT cost-saving needs. “For the modern-day CRM to be world class it needs to be revolutionary in market incursion and evolutionary in technological up gradation.” Today the major business focus is towards endowing value addition to the sales cycle, and customer retention rather than constructing a new customer base which is costlier and also an uncertain chase from business perspective. The basic philosophy behind CRM is that a company’srelationship with the customer would be the biggest asset in the long-run. It is now vital for CRM vendors to develop a sound understanding of their target organizations customer and deliver them with solutions which help in achieving long-term business relations with their customers. Vendors must also build long-term customer relationship management strategies with the end-user organizations to assure a series of deployments, and hence ensuring a regular revenue stream for themselves as well as their customers
System metadata — ISO 26324:2025, Annex B · DOI Handbook 10.1
Each element by the standard's name (Annex B: reference elements, then administrative) and the Handbook's (in grey), read off the record above.
| Element | Value | In the record |
|---|---|---|
| DOI Name DOI name | 10.46243/jst.2027.v2.i02.pp49-60 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | Impact of Customer Relationship Management in Retailing Sector -With Special Reference to Big Bazaar-An Empirical Evidence. (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | author: Dr.Zia Ur Rehman author: P.Anupama author: N. Krishnaveni publisher: Longman Publishers published: 2017-03-01 part of: Journal of Science & Technology · ISSN 2456-5660 · vol. 02 · no. 02 · pp. 49–60 language: en form: Digital · Visual · Language | agents, dates, container, language, structural_type, modes, characters |
| Referent Identifier(s) alternateIdentifier(s) | none besides the DOI | identifiers, relations (IsSameAs) |
| Registration Authority registrationAuthorityCode | Crossref — issued by Crossref (member 25296); held here as a copy | record.source_agency (our code, ra_doi_name, for names issued here once appointed) |
| Created Date issueDate | 2026-09-08 | record.registered (when the DOI name was first registered) |
| relatedIdentifiers | none needed — the descriptive metadata is in this record | container, relations (only where the descriptive metadata lives at another identifier) |
complete Every System Metadata element is here, with the basic metadata a journal article needs.
The System Metadata Declaration (JSON) · the Kernel Metadata Declaration (XML) · what each sub-type needs
History — the ledger
Every change to this DOI, in order, as it was recorded. Entries are only ever added, never changed or removed.
| # | When | What | By | Changes |
|---|---|---|---|---|
| 1 | 29 Sep 2026, 10:00 PM | register registered at Crossref; record read from api.crossref.org | Administrator (admin) | 78 fields set · sha256 490aaf07a2f7… |
| 2 | 29 Sep 2026, 11:59 PM | update record re-read from api.crossref.org | Administrator (admin) | container.titles.0.value: |
Machine-readable: the history as JSON, with the full record after each change.
